Skip to main content
Glama
kaminari-ad

@kaminari-ad/mcp

Official
by kaminari-ad

Unarchive Campaign

unarchive_campaign
Idempotent

Restore an archived campaign to default lists and resume scheduled runs.

Instructions

Restore an archived campaign. Inverse of archive_campaign. The campaign re-appears in default lists; if schedule_enabled was true, the scheduler resumes producing runs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesCampaign UUID.

Implementation Reference

  • The Tool object definition containing the `handler` function that calls `ctx.api.unarchiveCampaign(input.campaign_id)` to restore an archived campaign.
    export const unarchiveCampaignTool: Tool<UnarchiveCampaignInputShape, UnarchiveCampaignOutput> = {
      name: "unarchive_campaign",
      description:
        "Restore an archived campaign. Inverse of `archive_campaign`. The campaign re-appears in default lists; if `schedule_enabled` was true, the scheduler resumes producing runs.",
      annotations: {
        title: "Unarchive Campaign",
        readOnlyHint: false,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false,
      },
      inputSchema: z.object(UnarchiveCampaignInputShape),
      handler: async (input, ctx): Promise<Result<UnarchiveCampaignOutput, ToolError>> => {
        const result = await ctx.api.unarchiveCampaign(input.campaign_id);
        if (result.isErr()) return err(mapApiError(result.error));
        return ok(result.value);
      },
    };
  • Input schema: requires `campaign_id` (UUID string). Output type: `CampaignResponse`.
    const UnarchiveCampaignInputShape = {
      campaign_id: z.string().uuid().describe("Campaign UUID."),
    } as const;
    type UnarchiveCampaignInputShape = typeof UnarchiveCampaignInputShape;
  • Registration call: `register(unarchiveCampaignTool)` inside `registerAllTools()`.
    register(unarchiveCampaignTool);
  • HTTP API gateway implementation: calls POST /api/v1/campaigns/{campaign_id}/unarchive.
    async unarchiveCampaign(id: string): Promise<Result<CampaignResponse, ApiError>> {
      return call(
        "POST",
        "/api/v1/campaigns/{campaign_id}/unarchive",
        { params: { path: { campaign_id: id } } },
        parseCampaign
      );
    },
  • Port/interface definition for `unarchiveCampaign` method.
    unarchiveCampaign(id: string): Promise<Result<CampaignResponse, ApiError>>;
Behavior5/5

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

Annotations indicate idempotent and not destructive. The description adds further behavioral details: the campaign reappears in default lists and the scheduler resumes if enabled, providing transparency beyond annotations.

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?

The description is two sentences, front-loading the purpose and efficiently explaining side effects. No superfluous information.

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 tool with one parameter and no output schema, the description covers the action, side effects, and relation to siblings. It does not mention prerequisites (e.g., campaign must be archived), but overall sufficient.

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?

The single parameter `campaign_id` is well-documented in the schema (100% coverage). The description does not add extra semantics beyond the schema, so baseline score of 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?

The description clearly states it restores an archived campaign, explicitly calls out it is the inverse of `archive_campaign`, and explains the effects, distinguishing it from sibling tools.

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?

The description provides clear context on when to use (to restore an archived campaign) and points to the inverse relation with `archive_campaign`, offering guidance on usage relative to a sibling. It does not explicitly list when not to use, but the purpose is well-defined.

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