pr-media-monitor · git:20260813.48597a3 · 2026-08-13 · sha256 ea333f0958fab643
pr-media-monitor git:20260813.48597a3A
Immutable. This exact content is served forever at /api/v1/blob/ea333f0958fab643.
--- name: pr-media-monitor description: "Track media coverage, press mentions, journalist activity, and industry narrative across news outlets, Twitter, and LinkedIn. Ideal for PR teams monitoring earned media, tracking campaign impact, and identifying journalist relationships." --- # PR & Media Monitor Track media coverage, press mentions, journalist activity, and industry narrative across news outlets, Twitter, and LinkedIn. Ideal for PR teams monitoring earned media, tracking campaign impact, and identifying journalist relationships. Read [the API map](references/sandbase-api-map.md) before selecting a capability. ## Call SandBase capabilities For every selected tool, call `sandbase_describe_tool` first and use only arguments in its current input schema. Then call `sandbase_call_tool` with the exact `tool_name`. ## Available Tools - `google_news_bulk_articles` - `tavily_search` - `twitter_web_search_timeline` - `linkedin_web_v2_user_posts` - `linkedin_web_v2_company_posts` ## Workflow 1. Understand the user's research question, target, and context. 2. Call `sandbase_describe_tool` for each selected tool to confirm parameter schema. 3. Call `sandbase_call_tool` with the exact tool_name and schema-defined arguments. 4. Synthesize findings into a clear, evidence-backed answer. 5. Cite sources, note evidence gaps, and separate observations from interpretations. ## Guidelines - Always call `sandbase_describe_tool` before using any capability. - Cite sources and preserve attribution (URLs, usernames, dates, metrics). - Separate factual observations from analysis and recommendations. - If data is unavailable, note the gap and continue with available evidence. - Read-only research only. Never take actions on platforms.