Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Run a saved query now

saved_queries_run

Starts a saved query run now instead of waiting for its schedule, returning the running job; check run and match lists for results.

Instructions

Start a run of a saved query now instead of waiting for its schedule. Paid: the run searches live and charges what its searches cost, up to the query's maxCreditsPerRun, when it finishes in about a minute. Answers at once with the run, still running; read saved_queries_runs_list and saved_queries_matches_list for the result. A paused, capped or broken query must be resumed first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "saved_queries_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe saved query's id.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Exceeds the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) by disclosing cost semantics (paid, billed for live searches, bounded by maxCreditsPerRun) and async behavior (answers immediately with a still-running run, results arrive later, ~1 minute). The only gap is what a run object looks like on return, which is acceptable with no output schema but would have completed a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Densely front-loaded: action, cost, latency/asynchrony, follow-up tools, prerequisite, in that order, with no filler. Minor friction from compressed phrasing ("Answers at once with the run, still running") that takes a beat to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers what matters for an async, paid, mutating-in-effect tool with no output schema: cost exposure, expected latency, where the result lands, and the blocked-state prerequisite. Only the shape of the returned run is left implicit, which the linked list tools largely resolve.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the input schema already explains id, context, llm_model, and conversation_id in detail, so the baseline of 3 applies. The description adds no parameter-level meaning of its own; notably it does not reinforce the conversation_id echo rule despite the polling workflow it describes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource: "Start a run of a saved query now instead of waiting for its schedule" distinguishes it from scheduled execution and from the read-side siblings (saved_queries_runs_list, saved_queries_matches_list), which are named explicitly. An agent can select this tool without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the use condition (run now rather than wait for the schedule), the follow-up path for retrieving the result (the two list tools), and a hard prerequisite that rules out a failed call: "A paused, capped or broken query must be resumed first." That covers when, what next, and when-not in three sentences.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools