Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

expresstribune_author

Fetch an Express Tribune author's public archive page as structured story cards. Use the canonical author URL and 1-based page number to browse more pages via the publisher's Next link.

Instructions

Get an Express Tribune author's public archive. Returns one page of story cards from a canonical public author archive. Page is 1-based; the publisher's Next link indicates another page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical author archive URL
pageNo1-based page number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses return shape ('one page of story cards'), pagination semantics ('Next link indicates another page') and 1-based paging, but says nothing about auth requirements, rate limits, or what happens on the last page.

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 short sentences, front-loaded with the purpose before the return-shape and pagination notes. Every sentence contributes, though the pagination fact is stated slightly redundantly.

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 2-parameter scraping tool with no annotations and no output schema, the description covers what is returned (a page of story cards) and how to advance pages. Minor gaps remain around return-field detail and pagination termination.

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 both parameters (url, page) are already documented, including '1-based page number'. The description's restatement of 1-based paging adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 and resource ('Get an Express Tribune author's public archive'), scoping it to one publisher so an agent can instantly distinguish it from the many other *_author siblings like wsj_author or vice_author. The scope ('public archive') is unambiguous.

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?

Usage is implied by the name and the phrase 'canonical public author archive', but there is no explicit when-to-use or when-not guidance and no routing to alternatives such as expresstribune_article for individual stories. Adequate but leaves the agent to infer the selection conditions.

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