Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get a saved query

saved_queries_get
Read-onlyIdempotent

Retrieve a saved social media query by ID to reuse or inspect its stored search criteria.

Instructions

Get one saved query by id.

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_get"
  }
}

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

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope, so the safety profile is covered. The description adds nothing beyond that: it does not mention that the call is analytics-instrumented, that context and llm_model are mandatory, or that conversation_id must be echoed before any parallel calls are issued.

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?

One short, front-loaded sentence with zero filler. Its brevity is efficient, though the same brevity is what leaves the usage and behavioral gaps noted elsewhere.

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

Completeness3/5

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

For a simple single-record read this is close to adequate, and the schema carries the required-parameter burden. Still, with three required parameters including a conversation_id choreography rule and no output schema, the description should say what is returned and flag the sequencing constraint rather than leaving it entirely to the schema.

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%, so the baseline of 3 applies; the schema fully documents id, context, llm_model, and conversation_id. The description's 'by id' adds only a minimal hint about which parameter drives the lookup.

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

Purpose3/5

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

The description states a verb and resource ('Get one saved query') and adds a scope cue ('by id', singular) that separates it from a list operation. However, it largely restates the name and title and does not distinguish it from adjacent siblings such as saved_queries_run or saved_queries_matches_list.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus saved_queries_list, saved_queries_run, or saved_queries_update. The agent must infer from the tool name alone that this is the lookup-by-identifier path.

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