Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

usage_recent_ips

Retrieve recent API client IP addresses for an authenticated user, ordered by last seen time, with optional time range and limit filters.

Instructions

Get current user's recent API client IPs. Returns recent client IP addresses observed for the JWT-authenticated user's product API traffic, ordered by last seen time. Console, billing, usage, and user-management endpoints are excluded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoCustom upper bound in RFC3339 format when range=custom
fromNoCustom lower bound in RFC3339 format when range=custom
limitNoMaximum IPs to return. Defaults to 20 and clamps to 100.
rangeNoTime range preset. Defaults to the current billing period.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / range / enum
      Added value: +[
+  "period",
+  "day",
+  "week",
+  "month",
+  "custom"
+]
  2. Addedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description must carry behavioral detail, and it does: it specifies JWT-authenticated user scope, product API traffic, ordering by last seen time, and excluded endpoint categories. It does not describe response structure, pagination, or failure behavior, but the read-only nature is evident from 'Get' and 'Returns.'

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?

Two dense sentences front-load the core purpose, followed by scoping exclusions and ordering. No filler or repetition of schema details.

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?

The description plus fully documented schema gives an agent enough to call the tool correctly: scope, auth, ordering, exclusions, and all optional parameters. The main gap is the absence of explicit response-shape information, and there is no output schema to fill that void.

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?

All four parameters are already fully documented in the input schema, including RFC3339 conditions, default limit, clamp, and range enum/default. The description adds no parameter-level meaning beyond this, so the baseline 3 applies.

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?

The description opens with a specific verb and resource: 'Get current user's recent API client IPs.' It then clarifies the scope (JWT-authenticated user's product API traffic) and explicitly lists excluded endpoint families, which helps disambiguate it from usage_* siblings.

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

Usage Guidelines4/5

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

The use case is clear—retrieve recent client IPs for the current user—and the exclusions provide context about what traffic is in scope. It does not explicitly name alternative sibling tools or state when not to use this tool, so it falls short of full guidance.

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