Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_ad_fb_page_delete

DestructiveIdempotent

Deletes a Facebook page connection from a location, disconnecting the specified page from that location's ad publishing setup.

Instructions

Delete page connection Remove a Facebook page connection from a location. Deprecated: use DELETE /ad-publishing/facebook/pages/{pageId} with header version: v4. Endpoint: DELETE /ad-publishing/facebook/page (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.write

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "locationId": "<locationId>",
      "pageId": "<pageId>"
    },
    "name": "ghl_ad_fb_page_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesFacebook page ID
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and openWorld=true, so the safety profile is covered. The description adds genuine context beyond that: the required OAuth scope adPublishing.write, the API version header (v3), the source spec, and the deprecation path. It could say more about what precisely is severed (page-to-location link only?) but it does disclose auth and versioning caveats.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action, then the deprecation warning, then endpoint/scope metadata. The first line repeats the title verbatim, which is mild redundancy, but the remaining lines each carry distinct information (deprecation, path, version header, scope).

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 two-param destructive delete with no output schema, the definition supplies everything an agent needs to call it correctly: required params via schema, auth scope, API version, and a migration path. The only minor gap is that it doesn't characterize the response or confirm the effect is limited to unlinking rather than deleting the page itself.

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% and both parameters are documented in-schema ('Facebook page ID', 'Location identifier'). The description adds no further meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource twice over: 'Delete page connection' and 'Remove a Facebook page connection from a location.' This clearly distinguishes it from sibling read/manage tools like ghl_ad_fb_page_list or ghl_ad_fb_page_set_default without opening any schema.

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?

Explicitly flags the tool as deprecated and names the replacement endpoint (DELETE /ad-publishing/facebook/pages/{pageId} with header version: v4), which is strong routing guidance. It stops short of naming a sibling tool as the alternative and does not state exclusions in 'when-not' terms, so it is a 4 rather than a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools