Skip to main content
Glama

delete_rf_prediction

Delete a reach and frequency prediction in Meta Ads Manager. This action permanently removes the prediction.

Instructions

Delete a reach & frequency prediction. This action is irreversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prediction_idYesPrediction ID to delete

Implementation Reference

  • The actual handler function for the 'delete_rf_prediction' tool. It calls client.delete with the prediction_id and returns success/error response.
    // ─── delete_rf_prediction ─────────────────────────────────────
    server.tool(
      "delete_rf_prediction",
      "Delete a reach & frequency prediction. This action is irreversible.",
      {
        prediction_id: z.string().describe("Prediction ID to delete"),
      },
      async ({ prediction_id }) => {
        try {
          const { data, rateLimit } = await client.delete(`/${prediction_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 the 'delete_rf_prediction' tool: requires a single string parameter 'prediction_id'.
    {
      prediction_id: z.string().describe("Prediction ID to delete"),
    },
  • Registration of the tool via server.tool() with name 'delete_rf_prediction' and description 'Delete a reach & frequency prediction. This action is irreversible.'
    server.tool(
      "delete_rf_prediction",
  • src/index.ts:83-83 (registration)
    Top-level registration: registerReachFrequencyTools(server, client) is called, which registers all reach/frequency tools including delete_rf_prediction.
    registerReachFrequencyTools(server, client);
Behavior4/5

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

Discloses key behavioral trait 'irreversible' beyond annotations (which are absent). No information on permissions or side effects, but adequate for a simple delete.

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, front-loaded purpose, no fluff. Every word earns its place.

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 delete tool with one parameter and no output schema, the description is sufficient. Adds irreversibility context, though could mention how to obtain prediction_id.

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 parameter description 'Prediction ID to delete'. Tool description adds no extra meaning beyond that, baseline score of 3.

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 'Delete a reach & frequency prediction' - specific verb and resource, distinguishes from sibling tools like create_rf_prediction and get_rf_prediction.

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?

Indicates irreversibility, but does not explicitly state when to use or alternatives. Context is clear for a delete operation, no explicit exclusion.

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