redreplier

Get Monitored Website

get_website

Read-only

Retrieve a monitored website by ID to view all keywords and their statuses (PENDING, ACTIVE, DISABLED, SUSPENDED), and confirm changes after adding or activating keywords.

Instructions

Get one monitored website by ID with its full keyword list and statuses (PENDING, ACTIVE, DISABLED, SUSPENDED). Use it to re-check keyword statuses after add_keywords, enable_keyword, or activate_pending_keywords; use list_websites instead when you do not have the ID yet or want every site. websiteId comes from list_websites or create_website. Returns 404 when the website does not exist or belongs to another account, and 400 when websiteId is not a UUID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`websiteId`	Yes	Monitored website ID (UUID) from list_websites

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	The monitored website with its keyword list, each keyword carrying id, value, and status.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.1Sep 7, 2026

changedInput schema / properties / websiteId / description

Previous value: -"Monitored website ID (UUID)"New value: +"Monitored website ID (UUID) from list_websites"

changedOutput schema / properties / result / description

Previous value: -"The monitored website with its keywords and their statuses."New value: +"The monitored website with its keyword list, each keyword carrying id, value, and status."

First observedv0.1.0Sep 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds behavioral details about error responses (404 for non-existent or account-mismatched website, 400 for non-UUID), giving extra transparency beyond the annotations.

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 a single dense sentence that packs multiple pieces of information (purpose, usage guidance, parameter source, error details). While not overly long, it could be slightly more scannable. Still, every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description gives a good overview of what is returned ('full keyword list and statuses') and mentions error cases, but does not detail the output structure. Since an output schema exists, this is acceptable; the description provides sufficient context for calling the tool.

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?

The schema description covers the parameter completely, but the tool description adds valuable context by noting that websiteId 'comes from list_websites or create_website'. This extra semantic meaning helps the agent correctly source the parameter.

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?

The description states a specific verb ('Get') and resource ('monitored website by ID'), and explicitly mentions the included keyword list and statuses. It also distinguishes this tool from list_websites by specifying the use case, making it clear which tool to pick.

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?

The description explicitly tells when to use this tool ('re-check keyword statuses after add_keywords, enable_keyword, or activate_pending_keywords') and when not to ('use list_websites instead when you do not have the ID yet or want every site'). This provides unambiguous usage guidance.

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