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

ghl-mcp-server-v2

by zackscriven

ghl_social_delete_csv_post

DestructiveIdempotent

Deletes a specific post from a CSV social-media import by location, CSV, and post IDs, removing unwanted scheduled content from the import queue.

Instructions

Delete CSV Post Delete a specific post from a CSV import Endpoint: DELETE /social-media-posting/{locationId}/csv/{csvId}/post/{postId} (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>",
      "postId": "<postId>",
      "csvId": "<csvId>"
    },
    "name": "ghl_social_delete_csv_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvIdYesCSV Id
postIdYesCSV Post Id
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/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 genuine context beyond that: the exact HTTP endpoint and version header, that a Sub-Account (location) token is required, and the exact OAuth scope socialplanner/csv.write — real setup/auth information an agent cannot get from annotations or schema. It stops short of saying whether deletion is permanent or whether related CSV state is affected.

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-loaded with the action, then endpoint, auth, and scope in a tight structured block; nearly every line carries information. The opening 'Delete CSV Post' line merely repeats the tool title and could be dropped.

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 three-parameter destructive delete with no output schema, the description covers purpose, endpoint, auth token type, and scope — enough to invoke correctly. Missing only sibling disambiguation and a note on the irreversibility/scope of deletion, which the destructiveHint annotation partially covers.

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 description coverage is 100%, so all three parameters (locationId, postId, csvId) are documented with examples in the schema. The description only restates the path structure; it adds no semantics such as ID format constraints or whether csvId must still be an open import. Baseline 3 is appropriate.

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+resource: 'Delete a specific post from a CSV import', with the concrete endpoint DELETE /social-media-posting/{locationId}/csv/{csvId}/post/{postId}. It does not, however, name or contrast with the nearby siblings ghl_social_delete_post or ghl_social_bulk_delete_planner_posts, so an agent must infer that 'csv' means posts created via a CSV import rather than ordinary planner posts.

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 'CSV import' framing implies when this tool applies, and the required Sub-Account token plus socialplanner/csv.write scope imply a prerequisite. But there is no explicit when-to-use/when-not-to-use guidance and no mention of the sibling delete tools that would be the wrong choice here.

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