Skip to main content
Glama

RedReplier

by com.redreplier
OverviewDiscussionsAdmin

Add Website to Monitor

create_website

Add a website to monitor across Reddit, Hacker News, X, Bluesky, and Facebook. 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; the rest stay PENDING when the current entitlement has no capacity. 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
NameRequiredDescriptionDefault
urlYesFull website URL (e.g. "https://example.com")
nameNoDisplay name for the website
keywordsNoInitial keywords, stored as PENDING; list_websites promotes those that fit the plan for free
descriptionNoProduct summary the AI scores every mention against; without it new mentions are not scored. Draft one with analyze_website
workspaceIdNoWorkspace 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

TableJSON Schema
NameRequiredDescriptionDefault
resultNoThe created website with its id, domain, description, and keywords (initial ones PENDING).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed3 schema fields changed
    • 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)."
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Far exceeds the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), which only establish that this is a non-destructive write. The description discloses duplicate-400 behavior, revival of deleted domains, the quota cost of an omitted description, the null-description consequence (unscored mentions with a specific reason string), PENDING keyword promotion timing, and background AI keyword addition.

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 action and platform scope, and every sentence carries non-redundant information. It is a single dense block, though, and the keyword/quota/description rules would scan faster as separated clauses or bullets.

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?

An output schema exists, so return shapes need not be documented, yet the description still covers the 400 cases an agent must handle and the follow-up tools for repairing a null description. Nothing an agent needs to call this correctly is missing.

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 is 3, and the description adds real meaning on top: it explains that omitting description triggers a URL scrape that consumes one AI generation, that scrape failure or exhausted quota yields a null description, and that keywords land in PENDING until promoted. This goes beyond the schema's terser parameter notes.

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 a website to monitor') and immediately scopes it across named platforms (Reddit, Hacker News, X, Bluesky, Facebook). An agent can distinguish it from update_website, delete_website, and analyze_website without opening any schema.

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 operational conditions: the domain must be new, a duplicate returns 400, and re-adding a deleted domain revives the record. It also routes the agent to update_website or analyze_website when the description ends up null. It does not frame when another sibling would be preferred as the primary action, but for a create tool that is inherent.

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

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