Skip to content

MCP read-only and write tools

Distinguish reading retained evidence from changing watchlists, collecting data, exporting records and authorizing native social actions.

Guides

What effect will this tool call actually have?

An agent connection exposes several workflows with different effects. Reading status is not the same as creating a watchlist, and tracking public posts is not following an account. Understand the operation and current scopes before invoking it. Keep the user's intended research task separate from unrelated native social-account permissions.

Effect-aware agent prompt
Before changing anything, identify whether this step reads retained evidence, changes collection, saves an audience or exports data. Use only the scope needed for my task. Research permission does not authorize native follows, messages or posts.
01 / Guides

Start with a read-only check

Use signals_status to inspect the workspace and available coverage. Discovery suggests accounts without saving a watchlist, while queries ask about evidence already retained. These operations should not be described as automatically initiating recurring tracking. Read the actual tool description and current result rather than assuming every question collects more data.

02 / Guides

Identify workspace mutations

Creating, adding, refreshing or pausing a watchlist changes workspace state and may affect collection. Check the intended accounts, source policy and budget before the call. Supported writes use request keys for safe retries; keep the same operation identity when retrying the same effect instead of creating another logically identical job.

03 / Guides

Treat delivery as its own capability

A saved audience and a downloaded export are different steps. Verify current export permission and use the authorized saved result. Do not broaden scopes or create an API key just because a read-only connection cannot export. Keep private result links and credentials out of public documents and model-written summaries intended for wider sharing.

04 / Guides

Keep native social actions separate

Tracking, querying or exporting does not grant permission to follow, subscribe, send messages or post. Those effects require their own supported capability, acting-account identity and exact authorization. Do not turn an audience research task into outreach because it seems like the next logical step. A connection proves identity and access only within its actual scope.

Keep the boundaries clear.

  • Workspace tracking is not a platform-side follow or subscription.
  • Retries of one supported write should preserve its operation identity.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage