More Good Reviews

Update Review Source

updateReviewSource

Idempotent

Update Review Source

Assign an existing review source to a review by slug. Returns 404 if the source slug is not found.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "source_slug": "<source_slug>"
    },
    "name": "updateReviewSource"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Unique numeric identifier for this review.
`source_slug`	Yes	Slug of an existing review source. Returns 404 if the slug is not found. Accepts at most 50 characters.

Output Schema

Name	Required	Description	Default
`code`	No	Application-level status code returned by this API.
`success`	No	Indicates whether the request completed successfully.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 26, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already cover read/write safety (readOnlyHint=false, destructiveHint=false, idempotentHint=true). The description adds one useful behavioral detail: 'Returns 404 if the source slug is not found.' However, it does not disclose what happens to any previously assigned source or other side effects beyond the annotation baseline.

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 core action and error behavior are expressed in two concise sentences. The only mild redundancy is the opening 'Update Review Source' line repeating the tool title, but the rest is front-loaded and free of filler.

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?

For a two-parameter tool with an output schema and safety annotations, the description covers the essential action, the requirement that the source already exists, and the 404 failure mode. It is sufficiently complete for an agent to know how to invoke the operation correctly, though it could note whether an existing assignment is replaced.

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

Parameters3/5

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

Schema description coverage is 100%, so the parameter descriptions already document id and source_slug. The description's mention of 'existing review source' and '404' largely repeats the schema's own text for source_slug, adding no new parameter-level meaning beyond what the input schema provides.

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 operation: 'Assign an existing review source to a review by slug.' This clearly identifies the verb (assign), resource (review source), and target (review), and distinguishes it from sibling tools like updateSource (which modifies source settings) or createSource (which creates sources).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage context is implied: use when you need to attach an existing review source to a review. However, it does not explicitly name alternatives or state when not to use this tool, unlike sibling tools such as updateSource or createSource, leaving the agent to infer the boundary.

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

All More Good Reviews 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?