Skip to main content
Glama

get_keywords_positions_history

Получить историю позиций ключевых слов по параметру поиска.

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": {
      "search_options_id": "<search_options_id>"
    },
    "name": "get_keywords_positions_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoКоличество элементов (максимум 1000).
offsetNoСмещение элементов.
date_toNoДата окончания периода в формате YYYY-MM-DD. По умолчанию сегодня.
date_fromNoДата начала периода в формате YYYY-MM-DD. По умолчанию месяц назад.
search_options_idYesИдентификатор параметра поиска.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • removedInput schema / properties / date_from / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / date_from / default
      Removed value: -null
    • removedInput schema / properties / date_from / title
      Removed value: -"Date From"
    • addedInput schema / properties / date_from / type
      Added value: +"string"
    • removedInput schema / properties / date_to / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / date_to / default
      Removed value: -null
    • removedInput schema / properties / date_to / title
      Removed value: -"Date To"
    • addedInput schema / properties / date_to / type
      Added value: +"string"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / search_options_id / title
      Removed value: -"Search Options Id"
    • removedInput schema / title
      Removed value: -"get_keywords_positions_historyArguments"
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about being a read-only operation, pagination behavior (limit/offset exist but only in the schema), or data-retention limits. Beyond restating the purpose, it contributes no behavioral context an agent could not get from the schema.

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?

A single front-loaded sentence with zero filler, which is structurally clean. It is arguably terse to the point of underspecification, which is a completeness issue rather than a conciseness one.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and all five parameters are fully documented in the schema. For a read tool with no annotations and multiple sibling position tools, the missing piece is routing guidance against those siblings, making the definition minimally viable rather than complete.

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 every parameter (search_options_id, date_from, date_to, limit, offset) is already documented with defaults and formats. The description adds only a light framing of search_options_id as the 'search parameter' scoping key, matching the baseline for a fully documented schema.

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 (get keyword position history) plus the scoping key ('по параметру поиска'), which lets an agent distinguish it from sibling position tools like get_position or check_positions that presumably return current values. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated.

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 word 'история' implies this is the historical/timeseries variant rather than a current-snapshot lookup, which hints at when to prefer it. However, there is no explicit statement of when to use it versus get_position/check_positions, and no prerequisites or exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources