Skip to main content
Glama

Get GitHub credential activity

get_github_credential_activity
Read-only

List the recent GitHub App installation activity events (webhooks received) for a GitHub credential, newest first. Use this to confirm the integration is alive and see what GitHub has been sending. Read-only.

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": {
      "credential_id": "<credential_id>"
    },
    "name": "get_github_credential_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum events to return (default 50, max 100).
credential_idYesUUID of the GitHub credential.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description's closing 'Read-only.' is largely redundant with that. It does add genuinely useful behavior beyond the annotations: results are ordered 'newest first' and the events are inbound webhooks. It says nothing about pagination, whether there is a cursor, or what an event record contains, which matters given there is no output schema.

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

Conciseness4/5

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

Three short sentences that front-load the scope and then the purpose. Little waste; the only redundant element is 'Read-only.', which merely restates the annotation. The ordering note is appropriately brief.

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 two-parameter, read-only list tool with no output schema, the description covers purpose, ordering, and when to reach for it. The main remaining gap is that an agent does not learn the shape of an event record or whether results are truncated at the limit, which would help it interpret the response.

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% — both credential_id (UUID of the GitHub credential) and limit (default 50, max 100) are documented in the schema. The description adds no parameter-specific meaning beyond that, so the baseline of 3 for fully covered schemas 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?

The description states a specific verb and resource: 'List the recent GitHub App installation activity events (webhooks received) for a GitHub credential.' That is concrete enough to distinguish it from generic credential tools like get_credential or list_credentials. However, it never names a sibling such as get_github_credential_usages or verify_github_credential, even though 'confirm the integration is alive' overlaps conceptually with verify_github_credential.

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?

It gives a clear when-to-use context: 'Use this to confirm the integration is alive and see what GitHub has been sending.' That tells the agent the diagnostic purpose. It stops short of explicit exclusions or pointing to the alternative to use for other cases (e.g., verifying credential validity vs. inspecting traffic), so it is strong but not a full 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.