RedReplier

Add Your Website

create_website

Add the user's own website to their RedReplier account so RedReplier can find public posts on Reddit, Hacker News, X, Bluesky, and Facebook that mention its keywords. 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 RedReplier reads the website's public homepage to write one, spending one AI generation from the plan quota; if that read 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 that step. Initial keywords are saved as PENDING and stay PENDING until add_keywords or enable_keyword activates them within the plan. 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

Name	Required	Description
`url`	Yes	Full website URL (e.g. "https://example.com")
`name`	No	Display name for the website
`keywords`	No	Initial keywords, saved as PENDING; activate them with add_keywords or enable_keyword
`description`	No	Product summary the AI scores every mention against; without it new mentions are not scored. Draft one with analyze_website
`workspaceId`	No	Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another

Output 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.

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / keywords / description

Previous value: -"Initial keywords, stored as PENDING; list_websites promotes those that fit the plan for free"New value: +"Initial keywords, saved as PENDING; activate them with add_keywords or enable_keyword"

Changed2 schema fields changedSep 28, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / workspaceId

Added value: +{
+  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another",
+  "type": "string"
+}

Changed3 schema fields changedSep 8, 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 observedSep 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing concrete failure modes: 400 on duplicate domain, 400 when plan slots are exhausted, revival of a domain deleted via delete_website, and the AI-generation quota cost of auto-drafting a description. It also explains the degraded path (description null, mentions unscored with reason string).

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-loaded with the core purpose, and nearly every clause carries operational information. It is dense and somewhat run-on in the middle, but there is little genuinely wasted text.

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 write tool with an output schema, this covers the remaining gaps an agent needs: prerequisite conditions (new domain, free slot), side effects (PENDING keywords, background AI suggestions), quota consumption, and the fallback state to check after the call.

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 baseline is 3, but the description adds real meaning: url must be a domain new to the account, description is the scoring context every mention is measured against (and what happens when omitted), and keywords land in PENDING until activated. This supplements rather than repeats the schema.

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 and resource ('Add the user's own website to their RedReplier account') plus the downstream effect (finding public posts on Reddit, Hacker News, X, Bluesky, Facebook). It is clearly distinguishable from sibling mutations like update_website and delete_website.

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?

The duplicate-returns-400 rule implicitly routes an agent to update_website for existing domains, and it explicitly names update_website/analyze_website for fixing a missing description and add_keywords/enable_keyword for activating PENDING keywords. It stops short of a crisp 'use this when / not when' statement, but the context is 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

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

Need Help?