Skip to main content
Glama
Sign In

TrueScrape

by io.github.TrueScrape
OverviewDiscussionsAdmin

Read found mentions

get_monitor_mentions
Read-only

Posts found by monitors, both term mentions and followed accounts' posts (source says which), newest first, 50 per page. New posts come first; those already out there when the monitor started follow, marked baseline: true. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_monitor_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch the stored title, text and author. Beside unread_only it filters without marking anything read. Unavailable to zero-retention teams, which store nothing.
sinceNoISO time: only posts first seen at or after it. A filter beside unread_only marks nothing read.
cursorNonextCursor from the previous page.
sourceNomention: found by searching the term. account: posted by a followed account.
platformNoOnly posts from this platform, such as reddit.
monitor_idNomonitorId from create_monitor or list_monitors. Omit for every monitor.
unread_onlyNoOnly what this API key has not read yet, oldest first, and mark it read. Two keys read independently. Baseline posts are never unread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint), yet the description adds real value: page size (50), ordering (newest first, with unread_only flipping to oldest first only in the schema), baseline semantics for pre-existing posts, and that calls are free. It does not mention that unread_only marks results read – a side effect disclosed only in the parameter schema.

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 clauses with no filler, and the core identity ('posts found by monitors') leads. Dense but readable; the baseline clause is slightly compressed in phrasing ('those already out there when the monitor started follow').

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?

With no output schema and all seven parameters documented in the schema, the description supplies what the schema cannot: pagination size, sort order, baseline meaning, and cost. Nearly complete, though the read-marking behavior of unread_only and cursor usage are left entirely to the schema.

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 the baseline is 3, but the description goes beyond it by explaining what 'baseline: true' actually means (posts that existed when the monitor started) and by clarifying that source distinguishes the two discovery paths. Ordering and page size, absent from the schema, are also supplied.

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 resource and scope: posts surfaced by monitors, covering both term mentions and followed-account posts. It is distinguishable from the sibling find_mentions by the 'found by monitors' framing, but it never names that alternative explicitly, so the contrast is implied rather than stated.

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 implied (read stored results from your monitors) and the word 'Free' hints at a cost advantage over the paid search-style siblings, but there is no explicit when-to-use/when-not or named alternative such as find_mentions or check_monitor. The agent must infer the routing decision.

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