Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

seattletimes_headlines

Retrieve Seattle Times section headlines by required slug, returning recent story titles, canonical URLs, summaries, publication times, and authors.

Instructions

Get Seattle Times section headlines. Returns about 30 to 35 of the latest Seattle Times stories for one section. section is required and takes a section slug such as seattle-news, politics, boeing-aerospace, mariners, seahawks or obituaries. Each item has its title, canonical URL without tracking parameters, summary, publication time and author. Only the newest page is available.

Input Schema

NameRequiredDescriptionDefault
sectionYesSeattle Times section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 and does reasonably well: it discloses item count (~30-35), the per-item fields, that URLs are canonical without tracking parameters, and the key limitation that only the newest page is available (no pagination/history). It omits rate limits or freshness/caching behavior, keeping it short of a 5.

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?

Four sentences, front-loaded with purpose before return details, then the required parameter, then the pagination limitation. Each sentence carries distinct information with no filler, though the parameter sentence is partially redundant with the enum.

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?

With no output schema, the description steps in to describe the return shape (title, URL, summary, publication time, author) and the volume cap, and it flags the single-page limitation. For a one-param, read-only news listing this is nearly complete; freshness and case-sensitivity of the slug are the only material gaps.

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 coverage is 100% and the schema already enumerates every valid slug, so the schema does the heavy lifting. The description's example slugs (seattle-news, politics, boeing-aerospace, mariners, seahawks, obituaries) reinforce that a slug is expected but add no syntax or format meaning beyond the enum. Baseline 3 is appropriate.

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?

States a specific verb (Get) and resource (Seattle Times section headlines) with the scoping constraint 'for one section' spelled out. It is clearly distinguishable from siblings such as seattletimes_article, seattletimes_author, and seattletimes_sections without opening any schema.

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 ('latest stories for one section', 'only the newest page is available') but never explicitly says when to choose this over alternatives like seattletimes_news or seattletimes_sections, nor states any exclusions. Usage is inferable but not directed.

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