Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_team_fixtures

Retrieve paginated older FotMob team fixtures using a team ID and cursor; continue until the cursor is empty or null.

Instructions

FotMob paginated team fixtures. Returns one page of older team matches. Start with the fixtures.previousFixturesUrl cursor from /fotmob/team, then pass each response's previous value as cursor until it is empty or null. Team ids are open-ended numeric ids discoverable through /fotmob/search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorYesOpaque cursor copied from fixtures.previousFixturesUrl in /fotmob/team or previous in the preceding response
team_idYesNumeric FotMob team id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that results are paginated, that it returns only one page of older matches, and gives the cursor-chaining and termination behavior. It omits auth, rate-limit, and return-shape details, which keeps it short of a 5.

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?

Three tight sentences, front-loaded with what it returns, then the cursor workflow, then id discovery. No redundant restatement of the schema.

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 two-parameter paginated tool with no output schema and no annotations, the description supplies everything needed to call it correctly: cursor origin, iteration rule, termination condition, and id source.

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% so the baseline is 3, but the description adds genuine meaning: cursor is sourced from fixtures.previousFixturesUrl or the prior response's previous field, and team_id is an open-ended numeric id discoverable via /fotmob/search.

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+resource (paginated team fixtures) and scopes it to 'older team matches', distinguishing it from siblings like fotmob_team and fotmob_matches. An agent can tell what this returns without opening the 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?

Explains the full call sequence: start with fixtures.previousFixturesUrl from /fotmob/team, then iterate using each response's previous value until empty/null. Clear context on how and when to invoke, though it does not name explicit alternative tools or state when not to use this instead of a non-paginated fixtures tool.

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

Deploy Server

Other Tools