Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List a saved query's matches

saved_queries_matches_list
Read-onlyIdempotent

List posts matched by a saved query, one page at a time, with optional filters for platform, time, sentiment, relevance, attention, and post kind.

Instructions

List the posts a saved query has matched, a page at a time, optionally by platform, time, sentiment or, with insights, relevance (relevant leaves out posts not about the topic), attention (needs_reply or risk) and kind. Every post is kept and listed unless a filter is given. Pass page.nextCursor back as cursor, with the same sort, for the next page. 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": {
      "id": "<id>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "saved_queries_matches_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOnly posts whose title or text contains this, ignoring case.
idYesThe saved query's id.
kindNoOnly matches insights judged to be this kind of post.
sortNo`posted` (default): the newest posts first, by when they were posted (or found, when the platform gave no time). `found`: the most recently found first, for keeping a copy in step.
limitNoMatches a page, up to 100. Default 50.
sinceNoOnly matches first seen at or after this time.
untilNoOnly matches first seen before this time.
authorNoOnly posts by this author: their handle as the post gives it (`author.handle`), without the `@`. Pair with `platform` when the same handle could be on several.
cursorNoThe `nextCursor` of the previous page, with the same `sort`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
platformNoA platform a search runs on: `twitter` (X), `reddit`, `youtube`, `tiktok`, `linkedin`, `instagram` (searched by hashtag, so only posts that use the hashtag are found), `threads` (searched by plain words, one short page a search, so it can miss posts) or `hackernews` (stories and comments). More platforms follow.
attentionNoOnly matches insights flagged as needing a reply, or as a risk.
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.
relevanceNoOnly matches with this relevance (a person's, where one was set, else the estimate); `relevant` is anything but `unrelated`. Matches without insights count as relevant.
sentimentNoOnly matches with this sentiment (a person's, where one was set, else the estimate).
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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: reads are free and served from prior-run storage, and "Every post is kept and listed unless a filter is given" discloses that there is no deduplication or truncation behind the caller's back. It does not describe the shape of a returned match record, which an agent must learn from the response itself.

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?

Four sentences, front-loaded with the operation and scope, then filters, then pagination, then cost. Nothing is filler. The filter sentence is slightly dense but readable.

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?

With 16 parameters, no output schema and a cursor-based paging contract, the description covers the critical return detail (page.nextCursor) but leaves the structure of a match record unexplained. It states that posts are neither dropped nor deduplicated, which is the most important behavioral fact, yet an agent still cannot predict what fields come back.

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 coverage is 100%, so every one of the 16 parameters already documents its own meaning and defaults. The description restates the filter families (platform, time, sentiment, relevance, attention, kind) and the sort/cursor coupling, but for the semantics of individual filters the schema does at least as much work. Baseline 3 applies.

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?

The description opens with a specific verb and resource: "List the posts a saved query has matched, a page at a time." It also enumerates the filter dimensions, so an agent knows this is a filtered listing of stored match records rather than a live search. It never names a sibling such as saved_queries_list or query_search_post, so differentiation relies on inference from the resource noun.

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

Usage Guidelines4/5

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

"Free: reads what earlier runs stored" tells the agent this is the non-billable path to already-collected results, and the pagination instruction ("Pass page.nextCursor back as cursor, with the same sort") tells it how to continue. What is missing is explicit routing guidance, e.g. when to prefer re-running the query versus reading stored matches.

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