Skip to main content
Glama

delete_canvas

Delete an Instant Experience (Canvas) by providing its ID. This action is permanent and irreversible.

Instructions

Delete an Instant Experience (Canvas). This action is irreversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
canvas_idYesCanvas ID to delete

Implementation Reference

  • The delete_canvas tool handler function. Calls client.delete with the canvas_id and returns success response, or catches errors.
    server.tool(
      "delete_canvas",
      "Delete an Instant Experience (Canvas). This action is irreversible.",
      {
        canvas_id: z.string().describe("Canvas ID to delete"),
      },
      async ({ canvas_id }) => {
        try {
          const { data, rateLimit } = await client.delete(`/${canvas_id}`);
          return { content: [{ type: "text" as const, text: JSON.stringify({ success: true, ...data as object, _rateLimit: rateLimit }, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
  • Input schema for delete_canvas: requires canvas_id (string).
    {
      canvas_id: z.string().describe("Canvas ID to delete"),
    },
  • The registerCanvasTools function is exported and registers canvas tools on the server.
    export function registerCanvasTools(server: McpServer, client: AdsClient): void {
  • src/index.ts:58-58 (registration)
    Where registerCanvasTools is called to register the tool on the MCP server.
    registerCanvasTools(server, client);
  • The client.delete method used by the handler to perform the HTTP DELETE request.
    async delete(
      path: string,
      params?: Record<string, unknown>
    ): Promise<ClientResponse> {
      return this.request("DELETE", path, params);
    }
Behavior2/5

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

While it mentions irreversibility, it lacks details on permissions, cascading effects, or error handling. With no annotations, more behavioral context is needed.

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?

Extremely concise, two sentences, front-loaded with action and resource. No wasted words.

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 no output schema and no annotations, the description is minimal. It lacks context on success/failure signals, required permissions, or what happens after deletion.

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 input schema already fully describes the parameter (canvas_id) with 100% coverage. The description adds no additional meaning beyond the schema.

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 the action ('delete') and the resource ('Instant Experience (Canvas)'), distinguishing it from sibling tools like delete_ad or delete_campaign.

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 on when to use this tool versus alternatives, no prerequisites, or context for deletion. Only states the action and irreversibility.

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/mikusnuz/meta-ads-mcp'

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