Skip to main content
Glama
Sign In

Keytomic

by com.keytomic.app
OverviewDiscussionsAdmin

Update Reddit settings

update_reddit_settings
DestructiveIdempotent

Saves the Reddit Opportunities settings of a site, the same as "Change topics" on the Reddit Opportunities page: the search topics (1 to topicLimit, from get_reddit_settings), the subreddit filter (empty: all subreddits) and the Agent Mode. Send every value the settings must have; the save replaces them. The next daily scan uses them; this tool starts no scan. A save with topics that are new to the site makes one AI call to write their search phrasings, as in the app. Read the current settings with get_reddit_settings first.

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": {
      "topics": "<topics>",
      "agentMode": "<agentMode>",
      "projectId": "<projectId>"
    },
    "name": "update_reddit_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicsYesSearch topics, at most topicLimit from get_reddit_settings.
agentModeYes"founder": replies speak as the founder. "user": replies speak as a user of the product.
projectIdYesSite to act on, from list_sites.
subredditsNoSubreddit names, with or without r/, such as "r/smallbusiness". Empty searches all subreddits.

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?

Goes well beyond the destructiveHint/idempotentHint annotations by disclosing that the save replaces all settings (omitted values are lost), that the next daily scan consumes the values while no scan is started now, and that new topics incur exactly one AI call to generate search phrasings. These are cost and side-effect details an agent cannot get 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?

Front-loads the core purpose, then layers constraints in a logical order (fields, replacement semantics, scan timing, AI cost, prerequisite read). Dense but nearly every sentence carries operational weight; the parenthetical "as in the app" is the only near-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 4-parameter write tool with no output schema, the definition covers replacement semantics, side effects, cost, and the required read-first workflow, leaving nothing an agent needs in order to call it correctly.

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 already 100%, and the description still adds meaning: the topic bound is tied to topicLimit from get_reddit_settings, an empty subreddits value means all subreddits, and the replace-all requirement reframes every parameter as mandatory to send. The agentMode enum meanings are left to the schema rather than expanded, which keeps it just short of a 5.

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+resource pairing (saves the Reddit Opportunities settings of a site) and enumerates exactly what is written: topics, subreddit filter, and Agent Mode. It also distinguishes itself from related siblings by anchoring to the in-app equivalent ("Change topics") and noting that it starts no scan, unlike scan_reddit.

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 directs the agent to call get_reddit_settings first, explains that the tool performs a full replacement ("Send every value the settings must have"), and rules out scan-triggering as an expectation. This covers when to use it, what prerequisite to satisfy, and a key non-behavior.

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