Skip to main content
Glama
Sign In

Highlightly

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Highlightly Highlights

highlightly_highlights
Read-onlyIdempotent

Video highlight links for a match (or for a date / league). Returns title, video url + embedUrl, source, and the associated match. Example: highlightly_highlights({ sport: "football", matchId: 123456, _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sport": "football",
      "_apiKey": "your-highlightly-api-key",
      "matchId": 123456
    },
    "name": "highlightly_highlights"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format to list highlights for (optional)
sportNoSport slug. Default "football" (soccer). "soccer" is normalized to "football".
_apiKeyYesHighlightly API key (free 100/day at highlightly.net)
matchIdNoNumeric match ID to fetch highlights for (optional)
leagueIdNoNumeric league ID to filter by (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds valuable behavioral detail on the return structure (title, video url + embedUrl, source, associated match) and provides an example, going beyond annotations without contradiction.

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?

The description is two concise sentences plus a short example. It front-loads the purpose, then lists return fields, and gives a concrete usage. There is no redundancy or fluff; every sentence earns its place.

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, the description explicitly lists the return fields, covering what an agent needs to expect. The input schema fully documents parameters, and the example clarifies invocation. For a read-only, idempotent tool with strong annotations, this is complete enough for correct usage.

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 all five parameters are already documented with type and meaning. The description includes an example, but it largely mirrors the schema examples and doesn't add semantic depth beyond what's already provided. Baseline 3 is appropriate given full schema coverage.

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 states a specific verb ('Returns') and resource ('Video highlight links for a match (or for a date / league)'), which clearly distinguishes it from siblings like highlightly_matches and highlightly_predictions. The example further clarifies the exact call pattern with sport and matchId.

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 provides clear context on when to use the tool (need video highlights for a match/date/league) and the return type, but does not explicitly name alternatives or state when not to use it. The purpose and scope imply the appropriate use, but there's no explicit exclusion.

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

All Highlightly toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources