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

ghl-mcp-server-v2

by zackscriven

ghl_social_csv_finalize

Finalizes a previously uploaded CSV import and schedules all its social posts for publishing, moving prepared CSV content into the publishing queue.

Instructions

Finalizes a previously uploaded CSV import and schedules all its posts for publishing (operationId start-csv-finalize). Start CSV Finalize Finalize a CSV import and schedule all posts for publishing Endpoint: PATCH /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>",
      "body": "<body>"
    },
    "name": "ghl_social_csv_finalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCSV Id
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnly=false, idempotent=false, destructive=false), and the description adds real context beyond them: a Sub-Account token is required and the socialplanner/csv.write OAuth scope is needed. It does not say whether finalization is reversible or what happens to the CSV after scheduling, which is the one remaining behavioral gap.

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

Conciseness3/5

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

The purpose sentence is front-loaded and clear, but the text then repeats itself almost verbatim ('Start CSV Finalize' / 'Finalize a CSV import and schedule all posts for publishing') and appends spec metadata. Roughly half the body is duplicated OpenAPI boilerplate.

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 three-parameter write endpoint with no output schema, the definition covers purpose, auth requirement, OAuth scope, endpoint, and version header — enough for an agent to call it correctly. Only the post-finalization side effects and the meaning of the body payload remain unaddressed.

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 all three required parameters (locationId, id, body.userId) carry descriptions, so the schema does the heavy lifting. The description adds nothing about parameter semantics, which is acceptable at full coverage but is baseline only.

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: finalizes a previously uploaded CSV import and schedules all its posts for publishing. The phrase 'previously uploaded CSV import' implicitly links it to the upload/list siblings, but it never names an alternative explicitly, so differentiation is inferential rather than stated.

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 prerequisite (a CSV must already have been uploaded) is implied by 'previously uploaded CSV import', which is genuinely useful. There is no explicit when-not guidance, no mention of what happens if the import was already finalized or of what the caller should do first/next.

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