Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Compare saved queries' share of voice

saved_queries_stats_compare
Read-onlyIdempotent

Compare 2–10 saved queries' post share of voice over the same UTC window, showing each query's overall and daily percentage of the combined total.

Instructions

Share of voice: 2 to 10 saved queries' posts over the same UTC days (default 30, up to 90), each as a share of their sum, overall and per day, in the order given. Only posts with a posting time count. Free: reads what earlier runs stored.

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": {
      "ids": "<ids>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "saved_queries_stats_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes2 to 10 saved query ids of this workspace, comma-separated (`sq_a,sq_b`) or repeated. A repeated id counts once.
nowNoThe window's last day is this time's UTC day, ISO 8601. Default: now. Send the same value to read the same window again.
daysNoUTC days to count, today (the day of `now`) included, from 1 to 90. Default 30.
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

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses two non-obvious behaviors: only posts with a posting time are counted, and the result is derived from what earlier runs stored (so freshness depends on prior runs). It does not explain what happens when no stored data exists for a requested id.

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?

Three short sentences, front-loaded with the definition, then the counting rule, then the cost/freshness note; nothing is padded. The phrasing 'each as a share of their sum, overall and per day' is slightly compressed but still parseable.

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?

For a read-only analytics tool with a fully documented six-parameter schema and no output schema, the description covers computation, window, counting rule, ordering, and cost. It stops short of describing edge cases such as insufficient stored data or a query with no posts in the window.

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 ids, days, and now are already fully documented, including the 2-10 bounds and the 30/90 day defaults that the description repeats. The only genuine addition is that results follow 'the order given', which clarifies that id ordering carries through to output.

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

Purpose4/5

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

States a specific computation ('share of voice') over a specific resource (2 to 10 saved queries' posts) with the exact output shape (share of their sum, overall and per day). It is clearly distinct from the sibling saved_queries_stats_get, though it never names that alternative explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: the 2-to-10 id requirement signals multi-query comparison, and 'Free: reads what earlier runs stored' hints at a cheap re-read of previously computed data. There is no explicit statement of when to pick this over saved_queries_stats_get, nor of what happens if the earlier runs are missing or stale.

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