Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

yahoo_sports_newsletters

Lists current public Yahoo Sports newsletter cards with slugs, archive URLs, and schedule/description text for catalog browsing without email signup.

Instructions

Yahoo Sports newsletter catalog. Lists the current public Yahoo Sports newsletter cards, including each newsletter slug, archive URL, and the schedule/description text shown by the site. This is a read-only catalog; it does not subscribe an email address.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "yahoo_sports_newsletters"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4/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 it reasonably: it declares the operation read-only, states explicitly that it does not subscribe an email address, and says results are the "current public" catalog. Missing only minor traits such as result count or ordering, which matters little for a parameterless catalog call.

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 short sentences, front-loaded with what the tool is and what it returns, followed by the one behavioral caveat. The final sentence is not filler: it prevents treating the tool as a subscribe action.

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?

There is no output schema and no input schema, so the description must describe the return shape, which it does by naming the newsletter slug, archive URL, and schedule/description text. Combined with the read-only caveat, an agent has everything needed to call this correctly.

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?

The tool takes zero parameters, so the baseline is 4. The description adds nothing about parameters because there are none to describe, and correctly frames the tool as a no-argument listing rather than one that would accept a filter.

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?

The description opens with a specific verb and resource: a catalog that "Lists the current public Yahoo Sports newsletter cards," and it enumerates the fields returned (slug, archive URL, schedule/description). It clearly states this is a catalog read, not a subscription action. It stops short of naming the closely related sibling yahoo_sports_newsletter_archive, so an agent must infer from "current" that this is the live catalog rather than the archive.

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?

"This is a read-only catalog; it does not subscribe an email address" usefully rules out one misreading, implying the tool is for discovery of newsletter slugs and archive links. However, no explicit when-to-use condition or named alternative (e.g., yahoo_sports_newsletter_archive) is given, so the routing decision is left to inference.

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