Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

techcrunch_author

Read-only

One TechCrunch staff writer or contributor's public profile: name, job title, headshot, biography, social links, and one page of their recent articles.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "techcrunch_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical techcrunch.com/author/<slug> URL
pageNo1-based page of recent articles to return; defaults to 1

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / page / description
      Added value: +"1-based page of recent articles to return; defaults to 1"
    • addedInput schema / properties / url / description
      Added value: +"Canonical techcrunch.com/author/<slug> URL"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the profile includes one page of recent articles and lists additional returned fields, but it does not disclose auth requirements, rate limits, or pagination behavior beyond what the schema provides.

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?

The description is a single front-loaded sentence that immediately identifies the resource and its contents. No words are wasted, and the most important information appears first.

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 an output schema present and annotations covering read-only/open-world behavior, the description need not explain return formats. It sufficiently describes the resource and its fields, though it omits guidance on when this author profile is preferable to related TechCrunch content tools.

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 the required canonical author URL and the optional page parameter are already documented in the schema. The description mentions 'one page' but does not add syntax or formatting details beyond the schema, making the baseline score of 3 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?

Names the specific resource (one TechCrunch staff writer or contributor's public profile) and enumerates the returned fields, including a page of recent articles. This clearly distinguishes it from sibling tools like techcrunch_article, techcrunch_headlines, techcrunch_news, and techcrunch_sections.

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 the tool is for fetching an author profile but gives no explicit when-to-use guidance, no when-not-to-use conditions, and does not route the agent between this tool and alternatives such as techcrunch_article or techcrunch_news.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources