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

ghl-mcp-server-v2

by zackscriven

ghl_social_get_csv_post

Read-onlyIdempotent

Fetch details of a specific CSV import and its posts, with skip and limit pagination for full result sets.

Instructions

Get CSV Post Get details of a specific CSV import including its posts Endpoint: GET /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.readonly Pagination params: skip, limit — pass them to page through full result sets.

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_get_csv_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCSV Id
skipNoNumber of records to skip
limitNoMaximum number of records to return
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / id / example
      Added value: +"65f92e55cc884f0d0845e447"
    • addedInput schema / properties / limit / example
      Added value: +"10"
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
    • addedInput schema / properties / skip / example
      Added value: +"0"
  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 read-only, idempotent, non-destructive behavior, so the description does not need to restate safety. It adds useful operational context beyond annotations: required Sub-Account token, OAuth scope, endpoint path, and pagination guidance.

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 description is front-loaded with the core purpose and remains reasonably compact. The endpoint/version/source metadata is somewhat implementation-facing, but it is not excessive and still supports correct invocation.

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 read-only tool with full schema coverage and annotations, the description covers endpoint, auth, scopes, and pagination. It does not describe response contents, but no output schema exists and the core invocation requirements are adequately covered.

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 four parameters are already documented. The description adds some guidance on skip/limit pagination and embeds locationId/id in the endpoint path, but it does not materially deepen semantics beyond the schema for the required parameters.

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?

The description states a specific verb and resource: get details of a specific CSV import, including its posts. The phrase 'CSV import' helps distinguish it from social post tools such as ghl_social_get_post, though it does not explicitly name sibling alternatives.

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 intended use is implied by 'Get details of a specific CSV import including its posts,' but there is no explicit guidance on when to use this versus ghl_social_csv_list or ghl_social_get_post. The auth and pagination notes provide context but not selection criteria.

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