Skip to main content
Glama

github_following

Default ~3 credits (limit 30; 0.1/result). Accounts a user follows — same card and ~0.1/row pricing as followers. Costs ~3 credits (0.1/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_following"
  }
}

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 30, max 100). Billed per result.
cursorNoOpaque cursor from a previous nextCursor (GitHub Link page=). Not a bare page number.
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 / 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."
  4. 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 (GitHub Link page=)."New value: +"Opaque cursor from a previous nextCursor (GitHub Link page=). Not a bare page number."
    • 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 100). Billed per result."
  5. Changed2 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 (GitHub Link page=)."
    • changedInput schema / properties / username / description
      Previous value: -"GitHub username or profile URL."New value: +"GitHub username or profile URL, e.g. getify."
  6. 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"
      +}
  7. 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."
  8. 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"
      +}
  9. Added

TDQS

B3.2/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 disclose genuinely useful behavior: the cost model (~3 credits, 0.1/result), that empty results and failures are never charged, and the 24h cache semantics with default-fresh behavior. Gaps remain around rate limits, ordering, and auth requirements, but billing and caching are the highest-risk unknowns for an agent and they are covered.

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 information is stated twice in the same paragraph: "Default ~3 credits (limit 30; 0.1/result)" followed by "Costs ~3 credits (0.1/result)", and the cache instruction is also restated. Roughly a third of the text is redundant, and the purpose is buried behind billing detail rather than front-loaded.

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 six-parameter read-only listing with a fully described schema and no output schema, the description supplies what structured fields cannot: cost, free-failure policy, and cache trade-off. It does not explain result ordering or pagination flow, but the cursor parameter's schema description covers the latter.

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 cache, limit, cursor, fields, compact, and username thoroughly. The description adds only an implicit restatement of limit=30 and the cache=true behavior, and the per-result billing note is the only meaning not already present in 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 states the resource as "Accounts a user follows", which with the tool name conveys the purpose, but it uses no explicit verb and never contrasts it with the sibling that returns the opposite relationship (github_followers). The phrase "same card and ~0.1/row pricing as followers" mentions a sibling only to align pricing, not to distinguish behavior.

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 only usage guidance is parameter-level: "Pass cache=true for a free 24h cache hit (default always fresh)." It does not say when to choose this tool over github_followers or github_user, nor any prerequisites. Usage is implied by the resource description rather than stated.

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.