Skip to main content
Glama
kaminari-ad

@kaminari-ad/mcp

Official
by kaminari-ad

List Campaigns (Picker)

list_campaigns_picker
Read-onlyIdempotent

Fetches a slim per-row campaign list (id, name, group_id, is_archived) for selection interfaces, avoiding heavy queries in large orgs. After selection, call get_campaign for full details.

Instructions

Slim per-row campaign list for selection UIs — id, name, group_id, is_archived. Cheaper than list_campaigns for orgs with thousands of campaigns. Use get_campaign(id) after a selection to fetch full details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool definition and handler function for list_campaigns_picker. It accepts no input (no params), calls ctx.api.listCampaignsPicker(), and returns a list of CampaignPickerItem (id, name, group_id, is_archived).
    export const listCampaignsPickerTool: Tool<
      ListCampaignsPickerInputShape,
      ListCampaignsPickerOutput
    > = {
      name: "list_campaigns_picker",
      description:
        "Slim per-row campaign list for selection UIs — id, name, group_id, is_archived. Cheaper than `list_campaigns` for orgs with thousands of campaigns. Use `get_campaign(id)` after a selection to fetch full details.",
      annotations: {
        title: "List Campaigns (Picker)",
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false,
      },
      inputSchema: z.object(ListCampaignsPickerInputShape),
      handler: async (_input, ctx): Promise<Result<ListCampaignsPickerOutput, ToolError>> => {
        const result = await ctx.api.listCampaignsPicker();
        if (result.isErr()) return err(mapApiError(result.error));
        return ok(result.value);
      },
    };
  • Input schema is an empty object (no parameters) and output type is readonly array of CampaignPickerItem.
    const ListCampaignsPickerInputShape = {} as const;
    type ListCampaignsPickerInputShape = typeof ListCampaignsPickerInputShape;
    
    export type ListCampaignsPickerOutput = readonly CampaignPickerItem[];
  • The tool is imported and registered via registerAllTools() at line 137.
    register(listCampaignsPickerTool);
  • Type definition for CampaignPickerItem — a pick of id, name, group_id, is_archived from the schema.
    export type CampaignPickerItem = Pick<
      S["CampaignPickerItem"],
      "id" | "name" | "group_id" | "is_archived"
    >;
  • Parser that validates and transforms the raw API response for the picker endpoint.
    const CampaignPickerSchema = schemas.CampaignPickerItem.pick({
      id: true,
      name: true,
      group_id: true,
      is_archived: true,
    }).strip();
    
    const CampaignPickerArraySchema = z.array(CampaignPickerSchema);
    
    export const parseCampaignPickerArray = (
      raw: unknown
    ): Result<readonly CampaignPickerItem[], ApiError> =>
      parseWithSchema(CampaignPickerArraySchema, raw, "campaigns-picker") as Result<
        readonly CampaignPickerItem[],
        ApiError
      >;
Behavior4/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it is cheaper and returns a slim list, which aligns with annotations and provides useful behavioral context without contradiction.

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?

Three sentences, each adding distinct value: what it does, when it's advantageous, and next step. No wasteful words; front-loaded with key information.

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

Completeness5/5

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

Given no parameters and no output schema, the description fully covers what the tool returns, when to use, and how to get more details. No gaps or missing context.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description confirms no inputs needed, which is sufficient; no additional parameter semantics are required.

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 specifies it is a slim per-row list for selection UIs, explicitly listing fields (id, name, group_id, is_archived) and contrasts with 'list_campaigns' by highlighting cost and use case, providing clear purpose and differentiation.

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

Usage Guidelines5/5

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

The description explicitly states when to use (for selection UIs, especially with thousands of campaigns) and when not to (use 'get_campaign(id)' for full details), offering clear alternatives and 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/kaminari-ad/mcp'

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