redreplier

Add Website to Monitor

create_website

Add a website to monitor and score keyword mentions across Reddit, Hacker News, X, and Bluesky. Provide a product description or let the server draft one to enable AI-scored leads.

Instructions

Add a website to monitor across Reddit, Hacker News, X, and Bluesky. The domain must be new to this account: a duplicate returns 400, and re-adding a domain removed with delete_website revives that record. description is the context every mention is scored against. Omit it and the server scrapes the URL to write one, spending one AI generation from the plan quota; if that scrape fails or the quota is exhausted the site is created with description null and its mentions go unscored (reason "Scoring skipped: website description missing"), so check the response and set one with update_website or analyze_website. Pass your own description to skip the scrape. Initial keywords are stored PENDING: list_websites or add_keywords promotes those that fit the plan for free, and activate_pending_keywords covers the rest, possibly for a charge. AI-suggested keywords are added in the background and show up on the website later. Returns 400 when the plan has no website slots left.

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, stored as PENDING; list_websites promotes those that fit the plan for free
`description`	No	Product summary the AI scores every mention against; without it new mentions are not scored. Draft one with analyze_website

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	The created website with its id, domain, description, and keywords (initial ones PENDING).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.1Sep 7, 2026

changedInput schema / properties / description / description

Previous value: -"Manual description (skips scraping/AI). Used as context when scoring mention relevance"New value: +"Product summary the AI scores every mention against; without it new mentions are not scored. Draft one with analyze_website"

changedInput schema / properties / keywords / description

Previous value: -"Initial keywords to monitor (added as PENDING)"New value: +"Initial keywords, stored as PENDING; list_websites promotes those that fit the plan for free"

changedOutput schema / properties / result / description

Previous value: -"The created website record with its description and initial keywords with their statuses."New value: +"The created website with its id, domain, description, and keywords (initial ones PENDING)."

First observedv0.1.0Sep 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Discloses side effects beyond the annotations: consumes an AI generation when description is omitted, creates the website, may return 400 on duplicate or slot exhaustion, and stores keywords as PENDING. Also mentions background AI-suggested keywords, providing clear transparency about what happens.

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 description is comprehensive but somewhat long; the purpose is front-loaded. Some redundancy exists between the omission and passing-your-own-description clauses, but overall it is organized and information-dense without being excessively verbose.

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 creation, error conditions, quota consumption, keyword lifecycle, and related tool usage, making it self-sufficient. The output schema is present, so return details are not required for completeness.

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

Parameters5/5

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

While the schema already describes parameters, the description adds crucial behavioral meaning: the description parameter is the scoring context and triggers scraping if omitted; keywords are stored PENDING and promoted via specific tools. This enriches the understanding of how each parameter affects the outcome.

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?

Clearly states the tool adds a website for monitoring across Reddit, Hacker News, X, and Bluesky, with the verb 'add' and resource 'website' being specific. This distinguishes it from siblings like update_website, delete_website, and list_websites.

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?

Names alternatives such as update_website, analyze_website, list_websites, add_keywords, and activate_pending_keywords, with conditions for when to use them (e.g., after creation if description is missing, or for keyword promotion). Explicitly notes duplicate and slot-limit errors, giving practical guidance on when this tool is appropriate.

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