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

ghl-mcp-server-v2

by zackscriven

ghl_snapshot_get_pushes_between_dates

Read-onlyIdempotent

Retrieves the sub-accounts where a specified snapshot was pushed during a date range, using an agency-level token and pagination for complete results.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only for all snapshots ops. from/to/lastDoc are required query params per spec despite generic-sounding names. Get Snapshot Push between Dates Get list of sub-accounts snapshot pushed in time period Endpoint: GET /snapshots/snapshot-status/{snapshotId} (Version header: v3; source: v3/snapshots-v3.json) Requires an Agency (company-level) token. Pagination params: 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": {
      "snapshotId": "<snapshotId>",
      "companyId": "<companyId>",
      "from": "<from>",
      "to": "<to>",
      "lastDoc": "<lastDoc>"
    },
    "name": "ghl_snapshot_get_pushes_between_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesOnly accepts ISO 8601 format
fromYesOnly accepts ISO 8601 format
limitNoLimit of documents to return. Default is 20
lastDocYesId for last document till what you want to skip
companyIdYes
snapshotIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real value: an agency-level token is mandatory for all snapshot operations, and limit is the pagination control for full result sets. It does not describe the shape or ordering of the returned push list.

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 token requirement is correctly front-loaded, but it is then repeated verbatim in a second sentence, and the endpoint/version/source line is noise for an agent. Roughly a third of the text is redundant.

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 6-parameter read-only tool with no output schema, the description covers auth scope, required query params, pagination, and the underlying endpoint, which is close to sufficient. It stops short of explaining what a 'push' record contains or whether limit is optional at call time.

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 67%, and the description usefully clarifies that from/to/lastDoc are required per spec despite generic names and that limit drives pagination. It adds nothing about the two undocumented parameters (companyId, snapshotId) beyond their presence in the path, so the coverage gap is only partly compensated.

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: list sub-accounts whose snapshot was pushed within a time period, via GET /snapshots/snapshot-status/{snapshotId}. It distinguishes itself from siblings like ghl_snapshot_get_latest_push by the date-range constraint, though it never names those siblings explicitly.

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 auth prerequisite (agency/company-level token) and the instruction to pass pagination params to page through results give usable context. However, it never says when to prefer this over ghl_snapshot_get_latest_push or ghl_snapshot_list, leaving the alternative-selection decision implicit.

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