Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fotmob_match_media

Retrieve public highlight-video and media metadata for a FotMob match using its numeric ID. Returns null source fields when media is unavailable.

Instructions

FotMob match videos and media metadata. Returns the public highlight-video and media metadata for one match. The request uses FotMob's English United States variant; unavailable media is represented by null source fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric FotMob match id, discoverable from /fotmob/matches or /fotmob/search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.6

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the request uses the English United States variant and that unavailable media is represented by null source fields, which is meaningful behavioral detail about the response. It stops short of stating auth needs or rate limits, but adds real value beyond the structured fields.

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 compact sentences, front-loaded with purpose first, then return content, then the locale/null behavior. No filler.

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

Completeness4/5

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

For a single-parameter read tool with no output schema and no annotations, the description covers purpose, return content, and null handling well. It could say more about how media is structured, but it is sufficient to invoke the tool correctly.

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% and there is a single required 'id' parameter already documented with discovery sources. The description adds no further syntax or format meaning for id, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Returns the public highlight-video and media metadata for one match.' An agent can tell it fetches media for a single match. It does not explicitly differentiate from close siblings like fotmob_match or flashscore_match_highlights, so it falls just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (fetch media for one match given an id) but gives no explicit when-to-use vs alternatives or prerequisites. Implied context only, with no exclusions.

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