Skip to main content
Glama

github_users_list_attestations_bulk

List attestations for a GitHub user filtered by subject digests, with pagination to navigate large result sets.

Instructions

List attestations by bulk subject digests

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesusername
per_pageNoThe number of results per page (max 100). For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."
beforeNoA cursor, as given in the [Link header](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api#using-link-headers). If specified, the query only searches for results before this cursor. For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."
afterNoA cursor, as given in the [Link header](https://docs.github.com/rest/guides/using-pagination-in-the-rest-api#using-link-headers). If specified, the query only searches for results after this cursor. For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."
bodyNoRequest body (JSON object)
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it fails to mention that this is a read-only operation, whether it supports pagination (despite schema having pagination parameters), or what the response structure is. The 'body' parameter implies a POST-like request, yet the tool is named 'list', creating ambiguity.

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?

At five words, the description is extremely concise but at the cost of clarity. It lacks structure and fails to front-load critical details. While brevity is valued, this level of conciseness underspecifies the tool for an AI agent.

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

Completeness2/5

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

Given the tool has 5 parameters, a nested 'body' object, and no output schema, the description is insufficient. It does not explain pagination, how to construct the request body, or what the response looks like. Sibling tools exist but no differentiation is provided.

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 describes each parameter. The description adds no additional meaning, such as how 'body' should be structured (e.g., an array of digests) or how 'before' and 'after' interact. It relies entirely on the schema, which is adequate but not enriched.

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 'List attestations by bulk subject digests', which identifies the action and resource but leaves 'bulk subject digests' undefined. It vaguely differentiates from the sibling 'github_users_list_attestations' but does not clarify what makes this 'bulk' version distinct or what a 'subject digest' is.

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?

No guidance is provided on when to use this tool versus alternatives like 'github_users_list_attestations' or 'github_users_delete_attestations_bulk'. The description lacks any context about prerequisites, scope, or typical use cases, leaving the agent to infer from the name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Eyalm321/github-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server