Skip to main content
Glama

List GitHub profile activity

github_profile_activity_list
Read-only

List recent public activity for a GitHub profile, one month per request. Accepts a username. Returns a list (use cursor when paginated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trimNoIgnored if this tool does not support it.
urlsNoAlias for `handle`. Prefer `handle`.
userNoAlias for `handle`. Prefer `handle`.
yearNoCalendar year to read activity for. Default: current calendar year.
limitNoIgnored if this tool does not support it.
cursorNoPagination cursor from a previous response (`data.page.nextCursor`). Pages backward one month at a time through the selected year.
handleNoGitHub username whose public activity timeline should be listed.
offsetNoIgnored if this tool does not support it.
contextYesDescribe the user's underlying goal in one sentence — not the tool you are calling.
pageSizeNoIgnored if this tool does not support it.
userNameNoAlias for `handle`. Prefer `handle`.
usernameNoAlias for `handle`. Prefer `handle`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
maxResultsNoIgnored if this tool does not support it.
profileUrlNoAlias for `handle`. Prefer `handle`.
linkedinUrlNoAlias for `handle`. Prefer `handle`.
max_resultsNoIgnored if this tool does not support it.
screen_nameNoAlias for `handle`. Prefer `handle`.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / linkedinUrl / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / linkedinUrl / type
      Removed value: -"string"
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / max_results
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / pageSize
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / profileUrl / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / profileUrl / type
      Removed value: -"string"
    • addedInput schema / properties / screen_name / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / screen_name / type
      Removed value: -"string"
    • addedInput schema / properties / trim
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Ignored if this tool does not support it."
      +}
    • addedInput schema / properties / urls
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "boolean"
      +    }
      +  ],
      +  "description": "Alias for `handle`. Prefer `handle`."
      +}
    • addedInput schema / properties / user / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / user / type
      Removed value: -"string"
    • addedInput schema / properties / userName / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / userName / type
      Removed value: -"string"
    • addedInput schema / properties / username / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  }
      +]
    • removedInput schema / properties / username / type
      Removed value: -"string"
  2. Changed2 schema fields changed
    • addedInput schema / properties / linkedinUrl
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / profileUrl
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
  3. Changed5 schema fields changed
    • addedInput schema / properties / screen_name
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / user
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / userName
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / username
      Added value: +{
      +  "description": "Alias for `handle`. Prefer `handle`.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "handle",
      -  "context",
      -  "llm_model"
      -]New value: +[
      +  "context",
      +  "llm_model"
      +]
  4. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "handle"
      -]New value: +[
      +  "handle",
      +  "context",
      +  "llm_model"
      +]
  5. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  6. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  7. Changed4 schema fields changed
    • removedInput schema / properties / year / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / year / maximum
      Added value: +2100
    • addedInput schema / properties / year / minimum
      Added value: +2008
    • addedInput schema / properties / year / type
      Added value: +"integer"
  8. Changed1 schema field changed
    • changedInput schema / properties / year / description
      Previous value: -"Calendar year to read activity for. Defaults to the current year when omitted."New value: +"Calendar year to read activity for. Default: current calendar year."
  9. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, which the description does not contradict. It adds valuable behavioral context beyond the annotations: the one-month granularity and the fact that pagination is cursor-based. This is useful for the agent and goes beyond the structured metadata.

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?

The description is three short sentences with zero fluff. Purpose is front-loaded, constraints are stated compactly, and every sentence earns its place. It's an example of minimal yet complete expression.

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?

Given there is no output schema, the description carries the burden of explaining the return format — it says 'Returns a list' and explains cursor pagination, which covers the key functional aspects. It could specify what the list contains (e.g., event types), but for a listing tool with clear annotations and sibling context, this is sufficient. A 4 reflects the minor gap in explicit output details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning by clarifying that a username (handle) is required, that activity is returned one month per request, and that cursor is for pagination. This supplements the schema's bare parameter definitions without redundancy.

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

Purpose5/5

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

The description states a specific verb and resource — 'List recent public activity for a GitHub profile' — and adds precise constraints: one month per request and cursor-based pagination. This clearly distinguishes it from sibling tools like github_profile_repositories_list or github_profile_followers_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on how the tool behaves — one month per request, cursor for pagination — but does not explicitly name alternatives or conditions for when to use this tool over its siblings. Context is clear, though exclusion criteria are absent, so a 4 rather than 5.

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.