Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_health_category

Fetch Yahoo Health section stories, including titles, URLs, categories, and thumbnails, with page-based pagination for a chosen health category.

Instructions

Yahoo Health section story stream. Returns a Yahoo Health section's editorial story feed: title, destination URL, category, and thumbnail image for each story, with page-based pagination. Sourced from Yahoo Health's own server-rendered section pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number, defaults to 1
categoryYesYahoo Health section

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / category / enum
      Added value: +[
+  "conditions",
+  "general",
+  "healthcare",
+  "treatments",
+  "wellness",
+  "your-body"
+]
  2. Addedv1.14.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It usefully discloses the return fields, page-based pagination, and the server-rendered source. However, it does not mention rate limits, authentication needs, or behavior on invalid page numbers, leaving some gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with no filler. The core purpose is front-loaded, and the source note adds useful context without bloating the description.

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 simple two-parameter read feed with no output schema, the description covers the essential return contents and pagination behavior. It lacks usage guidance and edge-case details, but an agent can correctly invoke the tool with the information provided.

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 both category and page are already documented in the schema. The description adds the concept of page-based pagination but no additional parameter-level syntax or format details beyond the schema.

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 clearly states the tool returns a Yahoo Health section's editorial story feed with specific fields (title, destination URL, category, thumbnail). It is distinct in function from siblings like yahoo_health_article and yahoo_health_home, though it does not explicitly name or contrast them.

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?

The description implies usage for retrieving a Yahoo Health section feed but provides no explicit guidance on when to choose this tool over alternatives such as yahoo_health_home or yahoo_health_article. No exclusions or selection criteria are given.

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