Skip to main content
Glama

github_campaigns_list_org_campaigns

Retrieve a paginated list of campaigns for a GitHub organization, with options to filter by state, sort by date fields, and control page size.

Instructions

List campaigns for an organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgYesorg
pageNoThe page number of the results to fetch. 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)."
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)."
directionNoThe direction to sort the results by.
stateNoIf specified, only campaigns with this state will be returned.
sortNoThe property by which to sort the results.

Implementation Reference

  • The handler function that executes the tool logic. It calls githubRequest to make a GET request to /orgs/{org}/campaigns with optional query parameters (page, per_page, direction, state, sort).
    handler: async (args: Record<string, any>) => {
      return githubRequest("GET", `/orgs/${args.org}/campaigns`, undefined, { page: args.page, per_page: args.per_page, direction: args.direction, state: args.state, sort: args.sort });
    },
  • Input schema definition using Zod, defining parameters: org (required string), page, per_page, direction (asc/desc), state (unknown), and sort (created/updated/ends_at/published).
    inputSchema: z.object({
      org: z.string().describe("org"),
      page: z.number().optional().describe("The page number of the results to fetch. 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).\""),
      per_page: z.number().optional().describe("The 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).\""),
      direction: z.enum(["asc", "desc"]).optional().describe("The direction to sort the results by."),
      state: z.unknown().optional().describe("If specified, only campaigns with this state will be returned."),
      sort: z.enum(["created", "updated", "ends_at", "published"]).optional().describe("The property by which to sort the results.")
    }),
  • The tool is defined as an object in the campaignsTools array with name 'github_campaigns_list_org_campaigns', along with its description, inputSchema, and handler.
    export const campaignsTools = [
      {
        name: "github_campaigns_list_org_campaigns",
        description: "List campaigns for an organization",
        inputSchema: z.object({
          org: z.string().describe("org"),
          page: z.number().optional().describe("The page number of the results to fetch. 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).\""),
          per_page: z.number().optional().describe("The 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).\""),
          direction: z.enum(["asc", "desc"]).optional().describe("The direction to sort the results by."),
          state: z.unknown().optional().describe("If specified, only campaigns with this state will be returned."),
          sort: z.enum(["created", "updated", "ends_at", "published"]).optional().describe("The property by which to sort the results.")
        }),
        handler: async (args: Record<string, any>) => {
          return githubRequest("GET", `/orgs/${args.org}/campaigns`, undefined, { page: args.page, per_page: args.per_page, direction: args.direction, state: args.state, sort: args.sort });
        },
      },
  • src/index.ts:110-130 (registration)
    The MCP server registration loop where all tools (including campaigns) are registered via server.tool() with name, description, schema, and execution handler.
    for (const tool of allTools) {
      server.tool(
        tool.name,
        tool.description,
        tool.inputSchema.shape as any,
        async (args: any) => {
          try {
            const result = await tool.handler(args as any);
            return {
              content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
            };
          } catch (err) {
            const message = err instanceof Error ? err.message : String(err);
            return {
              content: [{ type: "text" as const, text: `Error: ${message}` }],
              isError: true,
            };
          }
        }
      );
    }
  • The githubRequest helper function used by the handler to make authenticated HTTP requests to the GitHub REST API.
    export async function githubRequest<T>(
      method: string,
      path: string,
      body?: Record<string, unknown>,
      params?: Record<string, string | number | boolean | string[] | undefined>
    ): Promise<T> {
      const url = new URL(`${BASE_URL}${path}`);
    
      if (params) {
        for (const [key, value] of Object.entries(params)) {
          if (value === undefined || value === null || value === "") continue;
          if (Array.isArray(value)) {
            url.searchParams.set(key, value.join(","));
          } else {
            url.searchParams.set(key, String(value));
          }
        }
      }
    
      const headers: Record<string, string> = {
        Authorization: `Bearer ${getToken()}`,
        Accept: "application/vnd.github+json",
        "X-GitHub-Api-Version": "2022-11-28",
        "User-Agent": "github-mcp/1.0.0",
      };
    
      if (body) {
        headers["Content-Type"] = "application/json";
      }
    
      const res = await fetch(url.toString(), {
        method,
        headers,
        body: body ? JSON.stringify(body) : undefined,
      });
    
      if (!res.ok) {
        const text = await res.text().catch(() => "");
        let detail = text;
        try {
          const json = JSON.parse(text);
          detail = json.message || text;
          if (json.errors) detail += ` -- ${JSON.stringify(json.errors)}`;
        } catch {}
        throw new Error(`GitHub API error ${res.status}: ${detail}`);
      }
    
      if (res.status === 204) return {} as T;
    
      return res.json() as Promise<T>;
    }
Behavior2/5

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

Without annotations, the description should disclose behavioral traits. It merely states 'List campaigns' without mentioning pagination, filtering, rate limits, or that results are paginated—despite the schema containing page, per_page, state, and sort parameters.

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?

The description is a single, concise sentence. It is front-loaded and contains no unnecessary words, though it could benefit from slightly more detail without sacrificing brevity.

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 6 parameters, no output schema, and no annotations, the description is too minimal. It lacks information about the response format (e.g., that it returns a list of campaigns) and does not explain the filtering/pagination options.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for each parameter.

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 'List campaigns for an organization' is specific with a clear verb ('List') and resource ('campaigns for an organization'), and it distinguishes itself from other campaign-related tools like create, delete, get, and update.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., get_campaign_summary), nor does it mention any prerequisites or context.

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