Skip to main content
Glama

Find the pinned people's clearest claims on X

find_quote_moments
Destructive

One live X search over the pinned people's recent posts and clips; returns moments, each the person's own post with ONE clear claim, prediction or explanation, why this audience cares, and where in the clip it is. handles (X handles without @, 10-20 works best) replaces the pinned list; omit it to use the saved list. Takes up to ~2 minutes. Cost: the user's FIRST search is free and reads only the first 5 people (plan.free_find_available); after that 50 credits per search, reading everyone pinned — tell the user the cost and get a yes before a paid call. Then draft_quote_post for the moments the user likes. The user posts; never claim a post went out.

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": {
      "space_id": "<space_id>"
    },
    "name": "find_quote_moments"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOnly moments on this topic count, e.g. 'pricing'.
handlesNoX handles to pin, without @. Omit to search the saved list.
space_idYesThe content space (brand) to run it on — from list_content_spaces. No space yet? setup_content_space first.
window_daysNoHow far back to look (default 30).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: live open-world search, ~2 minute latency, the first search free but limited to 5 people via plan.free_find_available, then 50 credits per search — which explains why destructiveHint=true/readOnlyHint=false on an otherwise read-like operation. It also warns the agent never to claim a post went out.

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?

Front-loaded with purpose before cost and workflow, with no filler. Some cost/workflow clauses are packed into long semicolon-linked sentences, which is dense but still readable.

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?

Because there is no output schema, the description carries return-value duty and mostly delivers: the shape of a 'moment' and where it sits in a clip. It does not explain what happens when `handles` exceeds the practical range, or how topic filtering interacts with the free-tier 5-person limit.

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 the schema already documents all four parameters, including the omit-handles-to-use-saved-list behavior. The description adds one genuine detail ('10-20 handles works best'), but nothing about `topic` or `window_days` beyond what the schema says, so it lands at the baseline.

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?

States a concrete verb and resource: "One live X search over the pinned people's recent posts and clips" and names the output shape (moments, each the person's own post with ONE clear claim). It is clearly distinct from siblings like suggest_quote_people and draft_quote_post.

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 an explicit branch: supply `handles` to replace the pinned list, omit it to use the saved list. It also states the mandatory pre-call ritual (tell the user the cost, get a yes) and the follow-on step (draft_quote_post for moments the user likes).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.