RedReplier

Add Website to Monitor

create_website

Add a website to monitor across Reddit, Hacker News, X, and Bluesky. Keywords start as PENDING and only go live (ACTIVE) once they fit the plan — call activate_pending_keywords afterwards. The first website for an account also seeds keywords from the shared feed. If you omit description, the back-end scrapes and AI-generates one.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Full website URL (e.g. "https://example.com")
`name`	No	Display name for the website
`keywords`	No	Initial keywords to monitor (added as PENDING)
`description`	No	Manual description (skips scraping/AI). Used as context when scoring mention relevance

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	The created website record with its description and initial keywords with their statuses.

TDQS

A4.5/5.0

Behavior5/5

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

Adds meaningful side-effect detail beyond annotations: keywords are initially PENDING and only become ACTIVE after activation, the first website seeds keywords, and omitting description triggers scraping/AI generation. No contradiction with readOnlyHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with no filler; the most important creation semantics are front-loaded before the caveats. Every sentence 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?

Covers success outcome, pending/active lifecycle, the follow-up call, first-account edge case, and default behavior for an omitted description. With an output schema available, nothing needed for a correct call is missing.

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 description coverage is 100%, and most behavioral parameter details (PENDING keywords, description skipping scraping/AI) already appear in the input schema. The description reinforces them and adds the account-level seeding behavior, but doesn't materially expand parameter meaning.

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 ('Add') and resource ('website to monitor') plus the four platforms monitored. Clearly distinguishes from sibling update_website/delete_website/list_websites by naming the creation entry point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear sequencing context: keywords begin PENDING and require activate_pending_keywords afterwards, and the first website seeds keywords from the shared feed. It doesn't explicitly contrast with add_keywords, but the creation context and follow-up call make appropriate use clear.

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

All RedReplier tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool maps to a distinct resource and action: website CRUD, keyword lifecycle, mention queries/updates, alert settings, and billing previews. Even similar tools like list_mentions/count_mentions and activate_pending_keywords/preview_activate_pending are clearly separated as listing vs counting and action vs preview.

Naming Consistency4/5

The vast majority follow a clear verb_noun pattern (list_websites, create_website, update_mention_status, preview_keyword_billing). The only noticeable outlier is keyword_change_usage, which reads like a noun phrase instead of get_keyword_change_usage, and activate_pending_keywords/preview_activate_pending invert verb placement.

Tool Count4/5

21 tools is on the higher side for an MCP server, but the count is justified by the number of distinct resources (websites, keywords, mentions, alerts, billing) and the need for action/preview pairs. It feels slightly heavy but not bloated.

Completeness4/5

The server covers the core lifecycle for websites, keywords, mentions, alerts, and billing previews with no dead ends: create/list/update/delete resources and status transitions are all present. Minor gaps exist, such as no direct current-plan retrieval and no bulk mention status updates, but agents can work around these.

Resources

Need Help?