Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_social_delete_csv_post

DestructiveIdempotent

Delete a specific social media post imported via a CSV file, removing it from the scheduling 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)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
csvIdYesCSV Id
postIdYesCSV Post Id
locationIdYesLocation Id
Behavior3/5

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

Annotations (destructiveHint=true) already declare destructiveness; description adds context (CSV import) but no additional behavioral detail. Adequate but not enriched.

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?

Short and front-loaded with title, but includes endpoint details that are redundant; could be slightly more concise.

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

Completeness3/5

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

Simple delete operation; description covers basic purpose but lacks info on permanence or side effects, which is acceptable given annotations.

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 basic descriptions; description adds no further meaning beyond what schema provides, resulting in baseline score.

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 the action (delete) and resource (a specific post from a CSV import) with endpoint, distinguishing it from sibling delete tools like ghl_social_delete_post.

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 like ghl_social_delete_post; no prerequisites or exclusions mentioned.

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/zackscriven/ghl-mcp-server'

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