Skip to main content
Glama
NewsCatcher MCP

NewsCatcher MCP

Official

Save a company list

save_company_list
Idempotent

Create a reusable company list by website domain or add companies to an existing list for watchlists, portfolios, and competitor tracking; reuse it across research and monitoring.

Instructions

Create a reusable list of companies (by website domain), or add companies to an existing list (give list_id). Use it for watchlists, portfolios, accounts or competitors that the user will research or monitor more than once: start_research(company_list_id) and create_monitor(company_list_id) use it, and a monitor follows later changes to the list. Give companies, or from_run_id to save the companies of a company research run. Each company is identified in the background (free).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_company_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoList name (new lists only), e.g. "Portfolio" or "Competitors".
list_idNoAdd to this existing list instead of creating a new one.
companiesNoCompanies by domain, e.g. ["stripe.com", {"domain":"wise.com","name":"Wise"}].
from_run_idNoSave the companies of this company research run as a new list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the write/idempotent/non-destructive profile, so the bar is lower, and the description still adds real context: background company identification and that it is free, plus the fact that monitors follow later changes to the list. It omits what happens on a duplicate list name or when list_id and from_run_id/companies conflict.

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 is front-loaded in the first clause and the remaining sentences each carry distinct information (use cases, downstream consumers, input alternatives, cost). It is a single dense paragraph that could be split into short mode-specific lines for faster scanning, but nothing is padding.

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?

Coverage of modes, downstream usage and cost is good for a four-parameter mutation tool. However, there is no output schema and the description never says what comes back, notably the new list_id that start_research and create_monitor require, which is the single most important return detail for chaining.

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%, setting baseline 3, and the description goes beyond it by explaining the mode-selection relationship between parameters: give list_id to append, give companies or from_run_id for a new list. It does not state that name is effectively required when no list_id is supplied, which remains implicit.

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 ('Create a reusable list of companies') and explicitly covers both operating modes: create-new vs. add-to-existing via list_id. It also distinguishes itself from the sibling tools that consume it (start_research, create_monitor), so an agent can tell what this tool owns versus what merely reads its output.

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 clear when-to-use rule ('watchlists, portfolios, accounts or competitors that the user will research or monitor more than once') and names the downstream tools that make it worthwhile. It does not distinguish the add-to-existing mode from the sibling edit_company_list, which is the one alternative an agent could plausibly confuse with it.

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