Skip to main content
Glama
Sign In

Keytomic

by com.keytomic.app
OverviewDiscussionsAdmin

List Reddit threads

list_reddit_threads
Read-only

Lists the Reddit threads the daily scans found for a site, the same as the Reddit Opportunities page. view "open": the open threads, newest first, each with its AI relevance score (0 to 100), why it fits, its Brand Mention Safety and its newest Reply Draft (null before one); a thread leaves the open list after maxAgeHours (get_reddit_settings). view "history": one page of the threads that left the open list, with their outcome (replied, done, hidden or not_answered), the reply the user copied, whether set_reddit_opportunity_status can restore them, outcomeCounts and foundByDay; outcomeCounts and foundByDay count UTC calendar days, so they can differ from the page, which counts the days of the browser time zone. Filter with outcome and search, and page with cursor and nextCursor. outcome, search and cursor are only for view "history"; with view "open" they give invalid_arguments. It reads saved data only: it starts no scan and calls no AI model. Nothing posts to Reddit: the user copies a reply and posts it. Spends no credits.

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": {
      "projectId": "<projectId>",
      "view": "<view>"
    },
    "name": "list_reddit_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYes"open": the open list. "history": the threads that left it.
cursorNoview "history" only: nextCursor from the previous page.
searchNoview "history" only: only threads whose title or subreddit holds this text, in any case.
outcomeNoview "history" only: only threads with this outcome.
projectIdYesSite to act on, from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/no-destructive annotations, it discloses that the tool reads saved data only, starts no scan, calls no AI model, posts nothing to Reddit and spends no credits — exactly the behavioral facts an agent needs before promising an action. It also flags the UTC-vs-browser-timezone mismatch between outcomeCounts/foundByDay and the returned page, a non-obvious trap that annotations cannot express.

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?

The core purpose is front-loaded in the first sentence and each sentence carries distinct information. It is dense and somewhat run-on, packing view definitions, filter limits, side-effect guarantees and counting caveats into one block, but almost nothing is filler.

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?

For a five-parameter read tool with no output schema, the description covers the two views, the per-thread fields returned, filtering, paging, the required projectId source (list_sites) and all side-effect expectations. An agent could invoke it correctly and set user expectations without any additional documentation.

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 would be 3, but the description adds meaning the schema lacks: nextCursor is the paging token, cursor/outcome/search are invalid with view "open", and the day-counting semantics of outcomeCounts and foundByDay differ from the page's. Only minor gaps remain, such as how search interacts with paging.

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?

The description opens with a specific verb+resource ("Lists the Reddit threads the daily scans found for a site") and pins the concept to a known UI surface ("the same as the Reddit Opportunities page"). It then defines the two views by their contents, so an agent can tell this apart from generate_reddit_reply or scan_reddit without opening the schema.

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?

It states which view to use for which question ("open" for current threads, "history" for threads that left the open list) and explicitly limits outcome, search and cursor to view "history", warning that they yield invalid_arguments otherwise. It also cross-references get_reddit_settings for maxAgeHours and set_reddit_opportunity_status for restore, giving concrete alternatives rather than leaving the agent to guess.

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

All Keytomic 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