redreplier

Update Monitored Website

update_website

Destructive

Update a monitored website's display name or scoring description to refine how AI evaluates new mentions. Omit fields to keep them unchanged; empty description clears it.

Instructions

Update a monitored website's display name and/or description. Only the fields you pass change: omitted fields keep their value, and an empty description clears it. The description is the context the AI scores every new mention against, so keep it an accurate summary of the product; mentions already scored are not rescored. Use analyze_website to draft a description from the live site before saving it here. URL and keywords cannot change through this tool: use add_keywords, edit_keyword, or disable_keyword for keywords. Returns the updated website with its keyword list.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New display name
`websiteId`	Yes	Monitored website ID (UUID)
`description`	No	New scoring context; an empty string clears it, omit to keep the current one

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	The updated website with its name, description, and keyword list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.1Sep 7, 2026

changedInput schema / properties / description / description

Previous value: -"New description (used for relevance scoring)"New value: +"New scoring context; an empty string clears it, omit to keep the current one"

changedOutput schema / properties / result / description

Previous value: -"The updated website record with its new name and description."New value: +"The updated website with its name, description, and keyword list."

First observedv0.1.0Sep 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already mark destructiveHint, and the description adds field-level behavior such as clearing via empty string and preserving omitted fields. It also discloses the scoring-context effect, though it does not explicitly state irreversibility beyond the annotation.

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?

The description is compact and well organized, with each sentence serving a purpose: what updates, partial-update semantics, scoring context, and limitations. No unnecessary wording.

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?

Provides enough context to call correctly: partial update behavior, clearing semantics, scoring implications, and unsupported fields. Return value is stated, and the output schema exists, so no further detail is required.

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 covers all three parameters with clear descriptions, but the tool description adds important semantics: only passed fields change and empty description clears. This goes beyond the schema's basic field descriptions.

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 action: updating a monitored website's display name and/or description. It distinguishes itself from sibling tools by explicitly noting that URL and keywords cannot be changed and pointing to analyze_website for drafting descriptions.

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?

Gives explicit when-to-use guidance: partial updates, omitted fields keep values, empty description clears it, and mentions not rescored. It also names alternatives for keyword changes, making the choice clear.

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