Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nationalpost_headlines

Fetch National Post section headlines by required slug (e.g., canada, hockey, deals), returning top stories; some sections include publication time and byline.

Instructions

Get National Post section headlines. Returns National Post headlines for one section; section is required and takes one of 45 slugs such as canada, hockey or deals. The top-level sections health, opinion, longreads, modern-life, travel, entertainment, shopping-essentials and sports return 10 stories with publication time and byline. Others return up to about 45 without either. Sponsored stories are left out.

Input Schema

NameRequiredDescriptionDefault
sectionYesNational Post section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that top-level sections return 10 stories with timestamp and byline whereas others return up to ~45 with neither, and that sponsored content is excluded. It stops short of stating ordering, freshness, or any rate/auth constraints, so not a full 5.

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 sentences, front-loaded verb+resource, then parameter requirement, then return-behavior nuance. No filler; every sentence adds information.

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 single-required-param, no-output-schema tool with no annotations, the description adequately covers purpose, required input, and return shape. Missing only freshness/ordering and any indication that the results are the current headlines.

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?

Schema coverage is 100% and the enum already lists all 45 slugs, but the description adds real meaning: the count of slugs, representative examples, and critically that different slug groups yield different story counts and metadata. That is genuine value beyond the field description 'National Post section slug'.

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 precise verb ('Get') and resource ('National Post section headlines') with scope ('for one section'). This cleanly distinguishes it from siblings like nationalpost_news, nationalpost_sections, and nationalpost_article without needing to open 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?

It implies usage by stating that a single section is queried and enumerating the sections, but it never says when to prefer this over nationalpost_news or nationalpost_sections, nor any exclusions. Usage is inferable but not spelled out.

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