Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

punch_author

Fetch a Punch author archive from a canonical URL, returning the author's name, about 30 recent articles, and total archive pages; unknown authors return not-found.

Instructions

Get a Punch author archive. Returns a Punch author's name and their most recent articles (the first archive page, about 30) from a canonical url (https://punchng.com/author/<slug>/). total_pages is the number of archive pages. Punch author pages have no biography, photo or social links, so none are returned. An unknown author returns not-found.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Punch author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 burden and does well: it discloses return contents (name + ~30 recent articles, first archive page), the total_pages field, explicitly notes that no bio/photo/social links are returned, and covers the unknown-author not-found case. It lacks auth/rate-limit detail but covers behavior and edge cases well.

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?

Front-loaded with the core purpose, then layered with return contents, pagination, negative facts, and the edge case. Four tight sentences with no filler, though the negative bio/photo sentence is slightly verbose.

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-param read tool with no output schema or annotations, the description covers what is returned, the URL input format, pagination, and failure behavior. Only auth/prerequisite context is missing, which is minor for a read-only archive fetch.

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% with one parameter, so baseline is 3; the description adds value beyond the schema's bare 'Canonical Punch author URL' by giving the exact URL template (https://punchng.com/author/<slug>/), clarifying what 'canonical' means in practice.

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 (Punch author archive) and distinguishes itself from siblings like punch_article/punch_headlines by focusing on an author's archive page. An agent can immediately tell what it retrieves without opening the 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?

Implies the use case (fetch an author's archive from a canonical URL) but gives no explicit when-to-use vs when-not guidance or mention of alternatives like punch_article. The URL format hint provides context but the routing condition is only inferred.

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