Retrieve paginated article feeds from FotMob team news pages. Provide a numeric team ID, then use start_index to navigate through up to 10,000 news items.
FotMob team news. Returns the paginated article feed shown on a public FotMob team news page. Team ids can be found with /fotmob/search or /fotmob/team.
| Name | Required | Description | Default |
|---|---|---|---|
| team_id | Yes | Numeric FotMob team id | |
| start_index | No | Zero-based news offset from 0 through 10000 |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It explicitly states the feed is public and paginated, implying no authentication and read-only retrieval. It does not detail ordering or invalid-team_id behavior, but for a straightforward read endpoint this is sufficient transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no wasted words. It front-loads the resource, then adds only two genuinely useful supporting facts: pagination and team-id discovery.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter read endpoint with no output schema, the description covers purpose, public access, pagination, and required-parameter discovery. It does not describe article ordering or fields, but those are secondary to correct invocation and selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds value by explaining how to obtain team_id via /fotmob/search or /fotmob/team. The start_index parameter is already fully documented as a zero-based offset from 0 through 10000, so no further clarification is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: "Returns the paginated article feed shown on a public FotMob team news page." It clearly identifies the tool as team-scoped news retrieval rather than a generic news or team-info endpoint, distinguishing it from siblings like fotmob_news and fotmob_team.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly conveys the intended use case: fetching a team's public news feed. It also gives actionable guidance for resolving the required team_id by directing the agent to /fotmob/search or /fotmob/team. It does not explicitly name exclusions or when-not-to-use alternatives, but the context is strong.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.