Skip to main content
Glama
NewsCatcher MCP

NewsCatcher MCP

Official

Edit a company list

edit_company_list
Destructive

Modify a saved company list: remove domains, correct a company's name or domain, rename the list, or delete it. Monitors following the list apply changes on their next run.

Instructions

Change a saved company list: remove companies, correct one that was identified as the wrong business (new domain, name or other names), rename the list, or delete it. To add companies use save_company_list(list_id=…). Monitors that follow the list pick up the change on their next run.

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": {
      "list_id": "<list_id>"
    },
    "name": "edit_company_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
deleteNoDelete the whole list (monitors following it keep their last companies).
removeNoDomains to remove.
renameNoNew list name.
correctNoFix one company's identity.
list_idYesThe list to change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false, and non-idempotency, so the risk profile is known. The description adds real value by disclosing the downstream effect ('Monitors that follow the list pick up the change on their next run'), but says nothing about irreversibility, permission requirements, or what happens when a 'correct' targets a domain not in the list.

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?

Two tight sentences, front-loaded with the operation list followed by the sibling hand-off and the side-effect note. The parenthetical '(new domain, name or other names)' restates schema fields slightly, but it earns its place by disambiguating 'correct'.

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

Completeness3/5

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

No output schema exists, so it would help to say what a successful edit returns or whether the mutated list is echoed back. Errors around correcting a domain that is not present, and whether multiple operations can be combined in one call, are also unstated. Still, the core call semantics and side effects are adequately covered.

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 coverage is 100% and each parameter carries its own description, so the baseline is 3. The description helpfully frames the four mutation parameters as a set of operations, and explains 'correct' as fixing one company identified as the wrong business, which clarifies the intent of the nested object beyond the field list.

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?

Names a specific verb ('Change a saved company list') and enumerates the four supported operations: remove, correct, rename, delete. It explicitly contrasts with saving/additions, so an agent can separate it from save_company_list without opening a 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 a concrete routing rule: 'To add companies use save_company_list(list_id=…).' That covers the main ambiguity with its closest sibling. No explicit exclusion for get_company_list vs. this tool, but the enumerations of allowed mutations make the boundary clear.

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