Skip to main content
Glama
Sign In

TrueScrape

by io.github.TrueScrape
OverviewDiscussionsAdmin

Find mentions of a term right now

find_mentions
Read-only

Search for a term (a brand, product, domain or competitor) across up to 10 social platforms once, keeping only posts that mention it. Costs 1 credit per platform that answers, even if nothing on it mentions the term; a failed or empty platform costs nothing. Stores nothing and schedules nothing: use create_monitor to keep watching. Reports what happened on each platform, so read sources before concluding there are no mentions.

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": {
      "term": "<term>"
    },
    "name": "find_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe word or phrase to find, up to 200 characters.
platformsNoOmit to search all of them. Fewer platforms cost less.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnly/openWorld; the description adds the non-obvious cost model (1 credit per platform that answers, even if it finds nothing; failed or empty platforms are free), the no-storage/no-scheduling semantics, and that per-platform outcomes are reported. These are exactly the traits an agent cannot infer from structured fields.

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 tight sentences, front-loaded with what it does, then cost, then the alternative. Dense but every clause carries information; the final clause is slightly awkwardly worded but still earns its place.

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

Completeness5/5

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

With no output schema, the description still tells the agent that per-platform outcomes are returned and should be inspected before drawing a negative conclusion. Cost, coverage, persistence, and the sibling alternative are all covered for a two-parameter tool.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are documented there; the description adds meaning by characterizing the term as a brand, product, domain, or competitor, and by framing the platform list as an 'up to 10' cost lever. It does not add format details for the term beyond the schema's 200-character limit.

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 specific verb (search/find), the resource (posts mentioning a term), and the scope (up to 10 social platforms, one-shot). It also implicitly distinguishes itself from the monitoring siblings by saying it searches 'once' and keeps only matching posts.

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?

Explicitly routes the agent: 'Stores nothing and schedules nothing: use create_monitor to keep watching.' It also gives an interpretation rule for the result ('read sources before concluding there are no mentions'), which is usage guidance, not just behavior.

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

All TrueScrape toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources