Skip to main content
Glama

News publishers

get_publishers
Read-only
List the news publishers World Feed Monitor reads, alphabetically, optionally for one country. Each has a key to pass as `publisher` to search_news or get_latest_news, its homepage, and its type and sector where classified.

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": "get_publishers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage, from 1.
countryNoCountry ISO code, two or three letters.
per_pageNoPublishers per page. Default 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint already signals a safe read operation, and the description adds useful behavior beyond annotations: alphabetical ordering, optional country filtering, and the returned fields (key, homepage, type, sector). It does not describe pagination behavior, though the schema covers page parameters.

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?

A single dense sentence with no wasted wording. It front-loads the core listing behavior and then explains the key fields an agent can expect.

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?

For a simple read-only listing tool with no output schema, the description sufficiently explains what is returned and how the publisher key connects to sibling tools. Pagination is handled by the schema, so no important context is missing.

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 schema already documents page, country, and per_page. The description only reinforces that country filtering is optional and that publisher keys are the intended output, adding little parameter meaning beyond the schema.

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 uses a specific verb and resource: 'List the news publishers World Feed Monitor reads, alphabetically, optionally for one country.' It also distinguishes the resource from search_news/get_latest_news by explaining that publisher keys are inputs to those tools.

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?

It clearly establishes the use case: discovering publisher keys before calling search_news or get_latest_news, optionally filtered by country. It does not explicitly state when not to use this tool or compare it against get_coverage, but the context is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources