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

ghl-mcp-server-v2

by zackscriven

ghl_social_delete_csv

DestructiveIdempotent

Deletes a CSV import and all its associated social posts for a location. Use it to remove a CSV batch and its posts by CSV ID.

Instructions

Delete CSV Delete a CSV import and all its associated posts Endpoint: DELETE /social-media-posting/{locationId}/csv/{id} (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/csv.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>",
      "id": "<id>"
    },
    "name": "ghl_social_delete_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCSV Id
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / id / example
      Added value: +"65f92e55cc884f0d0845e447"
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the deletion cascades to all associated posts, and it requires a Sub-Account (location) token plus the socialplanner/csv.write OAuth scope — auth prerequisites the annotations do not convey.

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?

The action and its cascade are front-loaded in the first two lines, with endpoint/auth metadata following. Slightly verbose with the version-header and source-file parenthetical, which costs little but earns little for an agent deciding whether to call it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive delete with no output schema, the description covers what is destroyed, the cascade scope, the auth/token type, and the required OAuth scope. An agent has everything needed to call it correctly and to warn about its blast radius.

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%, so both required parameters are already documented. The endpoint template ({locationId}/csv/{id}) hints that both are path parameters, but the description adds no format, sourcing, or edge-case detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Delete a CSV import') and adds the critical scope detail that all associated posts are removed too. This distinguishes it in substance from ghl_social_delete_csv_post, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The cascade note ('and all its associated posts') implies caution about when to use it, but there is no explicit when-to-use/when-not-to-use guidance and no pointer to the narrower alternatives like ghl_social_delete_csv_post or ghl_social_bulk_delete_planner_posts. Usage is left to inference.

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