Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_github_users_item

Retrieve a GitHub user by login from a dataset, including profile, activity metrics, influence tier, geo, social links, and flags; unknown logins return 404.

Instructions

Get a GitHub user from the dataset. Returns one GitHub user from the dataset by login, with profile fields (name, bio, company, blog, location, email), follower, repo and 30-day activity counts, influence_tier, rank_score, geo, linked social accounts and bot or organisation flags. An unknown login returns 404.

Input Schema

NameRequiredDescriptionDefault
loginYesGitHub login, max 128 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.8/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 enumerates the returned profile fields, follower/repo/activity counts, scoring fields, geo, social accounts, and bot/org flags, and discloses the 404-on-unknown-login behavior. It omits auth and rate-limit context but is otherwise behaviorally rich.

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?

Two dense sentences with zero waste: the action and scope are front-loaded, the returned fields enumerated, and the 404 behavior placed last. Every clause carries information.

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?

No output schema exists, but the description effectively previews the return shape via its field list, and the single required param plus 404 behavior are covered. Complete for a lookup tool, though it could state that a login is required to already be known.

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 coverage is 100% and the login parameter is fully documented, so the schema does the heavy lifting. The description confirms login is the lookup key and notes 404 on an unknown value, but adds little syntactic/format detail beyond the schema, so baseline 3 applies.

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 ('Get a GitHub user from the dataset... by login'), clearly a single-item lookup versus the sibling search/facets/nearby tools. However, it never explicitly names those siblings, so differentiation is inferred from the singular 'one user by login' wording rather than stated.

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 'by login' framing implies you already have an identifier and need the full record, which hints at when to use it. But there is no explicit 'use datasets_github_users_search to find a user first' guidance or any when-not to use this versus the search/nearby siblings.

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