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

ghl-mcp-server-v2

by zackscriven

ghl_social_get_statistics

Retrieve analytics for multiple social media accounts across platforms, using custom current and comparison date ranges or a default last-7-days period.

Instructions

Get Social Media Statistics Retrieve analytics data for multiple social media accounts. Supports custom date ranges for both the current period and a comparison period. If no date ranges are provided, defaults to the last 7 days (excluding today) with comparison to the previous 7 days. Endpoint: POST /social-media-posting/statistics (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/statistics.readonly

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>",
      "body": "<body>"
    },
    "name": "ghl_social_get_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation ID (also known as Sub-Account ID) for the business location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / currentRange / allOf
      Added value: +[
      +  {
      +    "properties": {
      +      "endDate": {
      +        "description": "End date (ISO 8601 format)",
      +        "example": "2025-01-07T23:59:59.999Z",
      +        "type": "string"
      +      },
      +      "startDate": {
      +        "description": "Start date (ISO 8601 format)",
      +        "example": "2025-01-01T00:00:00.000Z",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "startDate",
      +      "endDate"
      +    ],
      +    "title": "DateRangeDto",
      +    "type": "object"
      +  }
      +]
    • changedInput schema / properties / body / properties / currentRange / description
      Previous value: -"Custom date range for the current analytics period. If omitted, defaults to the last 7 days (excluding today) with automatic comparison to the previous 7 days."New value: +"Current date range for analytics. If not provided, defaults to the last 7 days (excluding today) with comparison to the previous 7 days."
    • addedInput schema / properties / body / properties / currentRange / example
      Added value: +{
      +  "endDate": "2025-01-07T23:59:59.999Z",
      +  "startDate": "2025-01-01T00:00:00.000Z"
      +}
    • removedInput schema / properties / body / properties / currentRange / properties
      Removed value: -{
      -  "endDate": {
      -    "description": "End date in ISO 8601 format. Must be after startDate.",
      -    "example": "2025-03-31T23:59:59.999Z",
      -    "format": "date-time",
      -    "type": "string"
      -  },
      -  "startDate": {
      -    "description": "Start date in ISO 8601 format.",
      -    "example": "2025-03-01T00:00:00.000Z",
      -    "format": "date-time",
      -    "type": "string"
      -  }
      -}
    • removedInput schema / properties / body / properties / currentRange / required
      Removed value: -[
      -  "startDate",
      -  "endDate"
      -]
    • removedInput schema / properties / body / properties / currentRange / type
      Removed value: -"object"
    • changedInput schema / properties / body / properties / platforms / description
      Previous value: -"Array of social media platforms to filter analytics by. If not provided, all platforms will be included. NOTE: Linkedin (PAGE only) and Tiktok (BUSINESS only) are supported."New value: +"Array of social media platforms to filter analytics by. If not provided, all platforms will be included."
    • changedInput schema / properties / body / properties / platforms / example
      Previous value: -[
      -  "facebook",
      -  "instagram"
      -]New value: +[
      +  "facebook",
      +  "instagram",
      +  "linkedin",
      +  "google",
      +  "pinterest",
      +  "youtube",
      +  "tiktok"
      +]
    • addedInput schema / properties / body / properties / prevRange / allOf
      Added value: +[
      +  {
      +    "properties": {
      +      "endDate": {
      +        "description": "End date (ISO 8601 format)",
      +        "example": "2025-01-07T23:59:59.999Z",
      +        "type": "string"
      +      },
      +      "startDate": {
      +        "description": "Start date (ISO 8601 format)",
      +        "example": "2025-01-01T00:00:00.000Z",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "startDate",
      +      "endDate"
      +    ],
      +    "title": "DateRangeDto",
      +    "type": "object"
      +  }
      +]
    • changedInput schema / properties / body / properties / prevRange / description
      Previous value: -"Comparison date range. Can only be provided when currentRange is also present. If omitted while currentRange is present, no comparison data is returned."New value: +"Comparison date range. If not provided, no comparison will be made."
    • addedInput schema / properties / body / properties / prevRange / example
      Added value: +{
      +  "endDate": "2024-12-31T23:59:59.999Z",
      +  "startDate": "2024-12-25T00:00:00.000Z"
      +}
    • removedInput schema / properties / body / properties / prevRange / properties
      Removed value: -{
      -  "endDate": {
      -    "description": "End date in ISO 8601 format. Must be after startDate.",
      -    "example": "2025-02-28T23:59:59.999Z",
      -    "format": "date-time",
      -    "type": "string"
      -  },
      -  "startDate": {
      -    "description": "Start date in ISO 8601 format.",
      -    "example": "2025-02-01T00:00:00.000Z",
      -    "format": "date-time",
      -    "type": "string"
      -  }
      -}
    • removedInput schema / properties / body / properties / prevRange / required
      Removed value: -[
      -  "startDate",
      -  "endDate"
      -]
    • removedInput schema / properties / body / properties / prevRange / type
      Removed value: -"object"
    • changedInput schema / properties / body / properties / profileIds / description
      Previous value: -"Array of connected social media account IDs to fetch analytics for. This can be found as 'profileId' in /accounts api."New value: +"Array of connected social media account IDs to fetch analytics for. Limited to 100 accounts maximum."
    • changedInput schema / properties / body / properties / profileIds / example
      Previous value: -[
      -  "67a5a9aa776c837de4aa5b12"
      -]New value: +[
      +  "6673d4f770801753dcafd7b8_SovchenxzWl9R3OFPgsj_9285776684082983366"
      +]
    • removedInput schema / properties / body / properties / profileIds / minItems
      Removed value: -1
    • removedInput schema / properties / body / required
      Removed value: -[
      -  "profileIds"
      -]
    • addedInput schema / properties / body / title
      Added value: +"GetAnalyticsBodyDTOV2"
    • changedInput schema / properties / locationId / description
      Previous value: -"Location ID"New value: +"Location ID (also known as Sub-Account ID) for the business location."
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the HTTP endpoint, that a Sub-Account (location) token is required, and the required OAuth scope (socialplanner/statistics.readonly). These are real preconditions an agent needs. It does not describe the shape of the returned analytics or any rate limits, which would round it out.

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 purpose and default behavior, then auth details. The 'Version header: v3; source: v3/social-planner-v3.json' fragment is internal noise that does not help tool selection, slightly diluting an otherwise tight description.

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-analytics endpoint with 100% schema coverage and no output schema, the description supplies the missing pieces an agent needs before calling: token type, OAuth scope, and default date window. It could say more about what metrics are returned, but the omission is minor given the rich request schema.

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%, including per-field documentation of platforms, profileIds (100 max), currentRange and prevRange, so the baseline is 3. The description's date-default sentence largely restates what currentRange already documents and adds no syntax or format detail beyond the schema.

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?

States a specific verb + resource ('Get/Retrieve analytics data for multiple social media accounts') and scopes it to the social planner statistics endpoint, which separates it from siblings like ghl_social_get_posts or ghl_social_get_account. The tool's job is clear without opening the schema.

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?

Usage context is implied rather than stated: it documents that omitting date ranges yields the last 7 days vs the previous 7 days, which is genuine default guidance. But there is no explicit 'use this when…/use X instead' guidance and no mention of related reporting siblings, so the agent must infer when this is the right analytics tool.

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