Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

github_user_following

List the public accounts a GitHub user follows by username, with pagination. Returns each account's login, ID, avatar, profile URL, and type for network or audience analysis.

Instructions

List who a GitHub user follows. Lists the public accounts a GitHub user follows, identified by the required username. Page with page and per_page (max 100). Each account has its 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?

No annotations are present, so the description carries the burden. It does disclose that only public accounts are returned and specifies pagination limits, which is useful, but it omits auth requirements, rate limits, and error behavior for what is effectively a read operation.

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 action, then scope, pagination, and return fields. Slightly redundant between the first two sentences ('List who a user follows' then 'Lists the public accounts...'), but overall tight and worth the space.

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 read tool with no output schema and no annotations, the description covers the key facts an agent needs: scope (public only), pagination, and the shape of returned fields. Missing only orthogonal details like auth or rate limits.

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 'max 100'. The description restates required username and the per_page cap without adding format or default details beyond the schema.

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?

States a specific verb and resource ('List who a GitHub user follows') and clarifies scope ('public accounts'). The direction of the relationship is clear, distinguishing it implicitly from the followers sibling, but it never names an alternative tool explicitly.

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?

The verb 'List' implies the use case, but the description offers no explicit when-to-use guidance, no exclusion conditions, and does not point to github_user_followers or github_search_users for adjacent needs. Usage 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