Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

techcrunch_headlines

Fetch TechCrunch category headlines by slug, returning each story's title, URL, summary, publication time, and author for one selected section.

Instructions

Get TechCrunch category headlines. Returns the latest TechCrunch stories for one category. section is required and takes one of 22 slugs such as artificial-intelligence, startups, venture, security, fintech, space or cryptocurrency. Each item has its title, URL, summary, publication time and author.

Input Schema

NameRequiredDescriptionDefault
sectionYesTechCrunch category slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

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 full behavioral burden. It usefully discloses that results are 'latest' stories and describes each item's fields (title, URL, summary, publication time, author), which helps since there is no output schema. However, it omits pagination, result count, authentication, rate limits, and error behavior, so it does not provide a complete behavioral picture.

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?

The description is short and front-loads the core action, with parameter and return details following in a logical order. The first two sentences overlap slightly ('Get category headlines' and 'Returns the latest stories for one category'), but the overall structure is efficient.

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 one-parameter headlines tool with no output schema, the description covers the required parameter, its allowed values, and the shape of returned items. It does not specify how many stories are returned or whether there is pagination, but those gaps are relatively minor given the tool's simplicity.

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 the baseline is 3. The description repeats that `section` is required and takes one of 22 slugs, even giving examples, but these examples are already present in the schema enum and add little semantic meaning beyond what the structured field provides.

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 states a specific verb and resource: get TechCrunch category headlines. It clarifies that it returns the latest stories for exactly one category, which distinguishes it from a generic article or author lookup. However, it does not explicitly contrast itself with sibling tools such as techcrunch_news or techcrunch_sections, so it falls short of a 5.

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 says what the tool returns but gives no explicit guidance on when to use it versus alternatives. There is no mention of techcrunch_news, techcrunch_sections, or techcrunch_article, and no exclusions or prerequisites are stated. Usage must be inferred from the tool name and description alone.

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