Skip to main content
Glama

github_activity

Default ~4 credits (limit 10; 0.4/result). Public events with typed payload (Push commits/ref, PR/issue action) — 90-event ceiling. Costs ~4 credits (0.4/result). Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "github_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
limitNoMax items to return (default 10, max 90). Billed per result.
cursorNoOpaque cursor from a previous nextCursor. Pagination stops after GitHub's 90-event public activity ceiling.
fieldsNoOptional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.
compactNoDefault true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body.
usernameYesGitHub username or profile URL, e.g. getify.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / compact / description
      Previous value: -"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body."New value: +"Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. On Threads, Facebook, Meta Ad Library and TikTok Shop tools request timings are dropped too. Pass false for the full body."
  2. Changed2 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
      +  "default": true,
      +  "description": "Default true here: drop signed media URLs (video, image, avatar links and their expiry stamps) to keep the response small. Ids, permalinks, dates, text and metrics stay. Pass false for the full body.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Optional comma-separated keys to keep on each result row (or on the object for single-item tools), e.g. id,url,publishedAt,engagement. Pagination keys are always kept. Does not change the price.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return (default 30, max 90). Billed per result."New value: +"Max items to return (default 10, max 90). Billed per result."
  4. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."
  5. Changed3 schema fields changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque cursor from previous nextCursor. Stops at 90-event ceiling."New value: +"Opaque cursor from a previous nextCursor. Pagination stops after GitHub's 90-event public activity ceiling."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 30, max 90. Billed per result."New value: +"Max items to return (default 30, max 90). Billed per result."
  6. Changed3 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor (page number as string). Leave empty for the first page; then pass the nextCursor value returned in the previous response."New value: +"Opaque cursor from previous nextCursor. Stops at 90-event ceiling."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 30, max 100. Billed per result."New value: +"Max items to return. Default 30, max 90. Billed per result."
    • changedInput schema / properties / username / description
      Previous value: -"GitHub username or profile URL."New value: +"GitHub username or profile URL, e.g. getify."
  7. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Pagination cursor (page number as string). Leave empty for the first page; then pass the nextCursor value returned in the previous response.",
      +  "type": "string"
      +}
  8. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."
  9. Changed1 schema field changed
    • addedInput schema / properties / cache
      Added value: +{
      +  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
      +  "type": "boolean"
      +}
  10. Added

TDQS

C2.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the cost model (~4 credits, 0.4/result), the 90-event public activity ceiling, and that 'Empty results and failures are never charged.' It omits auth/permission prerequisites and what happens for private or nonexistent accounts, which keeps it short of a 5.

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

Conciseness2/5

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

The pricing sentence is duplicated almost verbatim -- 'Default ~4 credits (limit 10; 0.4/result)' and later 'Costs ~4 credits (0.4/result)' -- and the phrase 'Default ~4 credits' is ambiguous about what the default refers to. Four short sentences carry only two distinct facts, so the text is padded rather than front-loaded.

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

Completeness3/5

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

For a read-only fetch with no output schema, the description covers cost, the 90-event ceiling, and caching, but never sketches the returned structure beyond 'typed payload (Push commits/ref, PR/issue action)' or how cursor pagination interacts with the ceiling. Adequate for calling the tool, incomplete for predicting its output.

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 all six parameters are already documented in structured form; the description mainly restates the limit default and the cache behavior. It adds a useful framing that results are billed per item, tying cost to the `limit` value, but contributes no new syntax or format detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource well -- 'Public events with typed payload (Push commits/ref, PR/issue action)' with a '90-event ceiling' -- but supplies no verb at all (fetch/list/return), leaving the agent to infer the operation from the tool name. The resource is specific; the action is not, and no sibling is named to sharpen the boundary against github_contributions or github_user.

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 statement of when to use this tool versus the many github_* siblings; the only conditional advice is about the cache parameter ('Pass cache=true for a free 24h cache hit'), which is parameter usage rather than tool selection. An agent must guess whether activity differs from contributions, pull requests, or user.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.