Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yardbarker_author

Fetch a Yardbarker author profile from a canonical URL to return the author's name, image, and recent stories.

Instructions

Get a Yardbarker author profile. Returns a Yardbarker author profile from a canonical author url of the form https://www.yardbarker.com/authors/<slug>/<id> (required). The response has the name, profile image when provided and linked recent stories. Biography text and pagination are not available.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Yardbarker author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does useful work: it discloses the return contents (name, profile image when provided, linked recent stories) and limitations (no biography, no pagination). It does not mention permissions, rate limits, or side effects, but for a simple read-only profile lookup this is reasonably transparent.

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 compact and front-loaded, with the purpose first and limits last. There is minor redundancy between 'Get a Yardbarker author profile' and 'Returns a Yardbarker author profile,' but nothing significant is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema and no annotations, the description is complete enough: it states the required input format and summarizes the response fields and missing features. An agent has what it needs to call the tool and understand the expected output shape.

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%, so the schema already documents the single parameter. The description adds meaningful value by specifying the canonical URL form `https://www.yardbarker.com/authors/<slug>/<id>`, which is more precise than the schema's 'Canonical Yardbarker author URL'.

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 gives a specific verb and resource: 'Get a Yardbarker author profile.' It is clear what the tool does, but it does not explicitly distinguish this from other Yardbarker tools such as yardbarker_article, yardbarker_headlines, or yardbarker_news.

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 states that a canonical author URL is required and notes that biography text and pagination are unavailable, which implies the intended narrow use case. However, it does not explicitly say when to choose this tool over sibling Yardbarker tools or other author-profile tools.

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