Skip to main content
Glama
kaminari-ad

@kaminari-ad/mcp

Official
by kaminari-ad

Archive Campaign Group

archive_campaign_group
Idempotent

Soft-delete a campaign group and every campaign within it. Prevents archiving the default group; move campaigns out first.

Instructions

Soft-delete the group AND every campaign in it. The default group cannot be archived; ask the user to move campaigns out first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesCampaign group UUID.

Implementation Reference

  • The tool definition (name, description, annotations, inputSchema) and the handler that calls ctx.api.archiveCampaignGroup(input.group_id) to soft-delete the group and all its campaigns.
    export const archiveCampaignGroupTool: Tool<
      ArchiveCampaignGroupInputShape,
      ArchiveCampaignGroupOutput
    > = {
      name: "archive_campaign_group",
      description:
        "Soft-delete the group AND every campaign in it. The default group cannot be archived; ask the user to move campaigns out first.",
      annotations: {
        title: "Archive Campaign Group",
        readOnlyHint: false,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false,
      },
      inputSchema: z.object(ArchiveCampaignGroupInputShape),
      handler: async (input, ctx): Promise<Result<ArchiveCampaignGroupOutput, ToolError>> => {
        const result = await ctx.api.archiveCampaignGroup(input.group_id);
        if (result.isErr()) return err(mapApiError(result.error));
        return ok(result.value);
      },
    };
  • Input schema: expects a UUID 'group_id' field. Output type is 'GroupActionResponse'.
    const ArchiveCampaignGroupInputShape = {
      group_id: z.string().uuid().describe("Campaign group UUID."),
    } as const;
    type ArchiveCampaignGroupInputShape = typeof ArchiveCampaignGroupInputShape;
  • Tool registered in the tool registry via register(archiveCampaignGroupTool).
    register(archiveCampaignGroupTool);
    register(unarchiveCampaignGroupTool);
  • Production HTTP gateway: sends POST to /api/v1/campaign-groups/{group_id}/archive.
    async archiveCampaignGroup(id: string): Promise<Result<GroupActionResponse, ApiError>> {
      return call(
        "POST",
        "/api/v1/campaign-groups/{group_id}/archive",
        { params: { path: { group_id: id } } },
        parseGroupAction
      );
    },
  • Fake/test gateway: records the call and returns a default GroupActionResponse.
    async archiveCampaignGroup(id) {
      push({ method: "archiveCampaignGroup", id });
      await Promise.resolve();
      return (
        state.responses.archiveCampaignGroup ??
        ok<GroupActionResponse, ApiError>(DEFAULT_GROUP_ACTION)
      );
    },
Behavior4/5

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

Description discloses cascading behavior (group + all campaigns) and the constraint on the default group, adding meaningful context beyond the annotations which only indicate idempotence and non-destructiveness.

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?

Two sentences with no unnecessary words. The critical information (soft-delete, scope, and constraint) is front-loaded and clearly communicated.

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 simple one-parameter tool with no output schema, the description is sufficiently complete. It covers the action, scope, and a key edge case. Could mention the existence of an unarchive tool for completeness.

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% with a clear description for group_id. The tool description does not add additional parameter semantics beyond what the schema already provides, so baseline 3 is appropriate.

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?

Description clearly states the tool performs a soft-delete on the group and all campaigns within it, distinguishing it from sibling tools like archive_campaign. The special case of the default group being unarchivable is also specified.

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?

Provides explicit guidance on when not to use (default group) and the required pre-condition (move campaigns out first). However, does not explicitly list alternative tools for archiving individual campaigns or other operations.

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