Skip to main content
Glama
localseodata

Local SEO Data

Official

history_get

Read-only

Retrieve a past call and its full response by request_id or history_search ID so you can reuse data you already paid for instead of buying it again.

Instructions

Returns one past call in full, including the response body exactly as it was returned at the time. Free (0 credits).

Takes the request_id from any previous response, or the id from history_search. This is how you read an answer you already paid for rather than buying it again.

A null body is not an error and not a missing call: the call happened, and its cost and timing are still there. response_data_omitted is "not_stored" and deliberately does not guess which of four causes applied — logging off for the account, a body over the size limit, a non-JSON body, or an endpoint whose response is never stored.

Input Schema

NameRequiredDescriptionDefault
idYesA request_id from a previous response, or an entry id from history_search.

Output Schema

NameRequiredDescriptionDefault
idYes
methodYes
paramsNo
endpointYes
created_atYes
error_codeYes
request_idYes
status_codeYes
credits_usedYes
response_dataNo
response_time_msYes
response_data_omittedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: it is free, null bodies are not errors, and response_data_omitted="not_stored" intentionally does not infer one of four possible causes. This is exactly the kind of operational context annotations do not provide.

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

Conciseness5/5

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

Front-loads the purpose and cost, then explains id sourcing, then addresses the null-body edge case. Every sentence carries useful information without repetition.

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

Completeness5/5

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

Given an output schema, annotations covering read-only safety, and a fully documented parameter, the description supplies the remaining important context: cost, id source, and non-error null body behavior.

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?

The schema has 100% description coverage and documents the single id parameter. The description repeats that the id comes from a previous response or history_search but does not add 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 and resource: returns one past call in full, including the response body as originally returned. It explicitly distinguishes this from history_search by saying where the id comes from and frames the value as reading an already-paid-for answer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains when to use it: with a request_id from a previous response or an id from history_search. It also gives the alternative implicitly by saying this reads an answer already paid for rather than buying it again.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.