Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

sofascore_event_highlights

Instructions

SofaScore event highlights. Returns the highlight videos attached to a match: title, subtitle (for example Full Highlights), video url, thumbnail, the publish time, whether it is the key highlight, and the countries it is restricted to when SofaScore limits it. media_type_code is SofaScore's own numeric code and is returned untranslated. Returns 404 when the match has no highlight videos, which includes matches that have not finished.

Input Schema

Name	Required	Description	Default
`id`	Yes	Numeric SofaScore event (match) id

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.12Oct 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the exact return fields, warns that media_type_code is an untranslated numeric code, and documents the 404 case (no highlights / match not finished). Auth, rate limits, and pagination are unstated, but the behavior of the operation is otherwise well covered.

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?

Two tight sentences, front-loaded with the tool's purpose and return payload. Every clause earns its place, including the media_type_code caveat and the 404 condition.

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?

With no output schema and no annotations, the description fully compensates by enumerating the returned fields and disclosing the failure condition. For a one-parameter read tool, nothing an agent needs to invoke it correctly 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% and the single 'id' parameter is already documented as the numeric SofaScore event id. The description adds no syntax, format, or meaning beyond the schema, so the baseline 3 applies.

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 and resource: it 'Returns the highlight videos attached to a match' and enumerates the returned fields. This clearly separates it from other sofascore_event_* tools (statistics, lineups, incidents). It does not, however, explicitly name or contrast a sibling, keeping it at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to call this versus alternatives like sofascore_event or flashscore_match_highlights. Usage is only implied by the match-id parameter. The 404 note is behavioral rather than a when-to-use rule, so no routing guidance is offered.

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

Deploy Server

sofascore_event_highlights

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools