Skip to main content

Choose MCP tools

SocQ supports a compact toolset for open-ended research and typed tools for known platforms or endpoints. Filtering controls which tool schemas your client loads, reducing context usage and making tool selection more predictable.

Choose a mode

If you are unsure which endpoint to use, start with compact mode. If your application always collects the same resource, use an exact-tool connection.

Compact mode

Connect to:
The client discovers an endpoint and submits it through socq_execute:
Use this mode when the client needs socq_search_endpoints and socq_describe_endpoint to choose among many capabilities.

Platform mode

Select one to five comma-separated platform slugs:
This exposes typed tools such as:
Platform slugs match the first segment of the API path, for example youtube, tiktok, and facebook-ad-library.

Exact-tool mode

Select one to thirty comma-separated tool identifiers without the socq_ prefix:
For tools=youtube_comments, the connection exposes:
Call the typed tool with API input fields directly:
Typed tools add three optional control fields: These are separate from business inputs such as results_limit. For example, results_limit: 100 requests up to 100 collected comments, while _result_limit: 25 limits the current response page to 25 records.

Naming rules

The mapping is deterministic:

Restrictions

  • platforms and tools cannot be combined in the same URL.
  • Platform mode accepts at most five platforms.
  • Exact-tool mode accepts at most thirty tools.
  • Filtering changes tool visibility only. Authentication, product availability, billing, API-key limits, and asynchronous task behavior remain unchanged.
  • Reconnect or restart the client after changing a filter so it refreshes tools/list.
To verify a filtered connection, ask the client to list its SocQ tools, then run one small collection and confirm that socq_get_task can read the returned task ID.