Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

github_user_followers

Retrieve a GitHub user's public followers by username, with page and per_page pagination, returning each follower's login, ID, avatar, profile URL, and account type.

Instructions

List a GitHub user's followers. Lists the public accounts that follow a GitHub user, identified by the required username. Page with page and per_page (max 100). Each follower has their login, id, avatar URL, profile URL and account type.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
per_pageNoResults per page (max 100)
usernameYesGitHub username

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses that only public accounts are returned, the pagination cap (max 100), and the fields each follower contains. However, it omits auth requirements, rate limits, ordering, and whether private followers appear for authenticated requests.

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?

Three sentences, front-loaded with the purpose, then scoping, then pagination and return shape. No redundant filler; every sentence contributes useful information, though the return-field list could be trimmed if an output schema existed.

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 low-complexity, read-only list tool with 100% schema coverage and no output schema, the description covers purpose, parameter usage, and return fields. Missing auth/rate-limit context is a minor gap given the public-data nature of the operation.

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 schema already documents `username`, `page`, and `per_page` including the max-100 constraint. The description essentially repeats that information (required username, per_page max 100) without adding syntax or format details beyond the schema, so the baseline 3 applies.

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 (List) and resource (a GitHub user's followers), then clarifies the resource as 'the public accounts that follow a GitHub user'. This naturally differentiates it from the sibling github_user_following without needing to name it.

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?

No when-to-use guidance or alternatives are provided. It never mentions the sibling github_user_following or any condition that would select this tool over others, leaving the agent to infer routing from the 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