Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

github_user_events

List a GitHub user's recent public events by username, including event type, repository, timestamp, and public flag. Supports pagination for browsing activity.

Instructions

List a GitHub user's recent public activity. Lists a GitHub user's recent public events, identified by the required username. Page with page and per_page (max 100). Each event has its id, event type such as PushEvent, repository name, timestamp and public flag.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the load and does well: it discloses that only public events are returned, that pagination uses page/per_page with a max of 100, and describes the returned fields (id, event type, repo, timestamp, public flag). It omits rate limits or auth requirements, but the read-scope return shape is clearly conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are near-duplicates, both restating 'List a GitHub user's recent public...', which wastes space. The pagination and return-shape details are useful but could be folded into a single tighter lead sentence.

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 compensates by enumerating the event fields an agent will receive. Combined with the pagination note, this is sufficient for a 3-parameter public listing tool, though rate-limit or scope caveats are absent.

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%, so the schema already documents all three parameters including the per_page max of 100. The description merely restates the max and the required username, adding no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 (List) and resource (GitHub user's recent public events), which is enough to separate it from siblings like github_user_repos or github_user_followers. It does not explicitly name those siblings, so it stops short of a 5.

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?

There is no guidance on when to use this tool versus other GitHub user tools. The only clue is the word 'events', leaving the agent to infer that this is for activity streams rather than profile data. No prerequisites or exclusions are offered.

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