Skip to main content
Glama
delano
by delano

get_mock_call_logs

Fetch mock server call logs filtered by time, status code, method, path, or response type. Supports pagination and optional inclusion of request/response details.

Instructions

Get mock call logs. Maximum 6.5MB or 100 call logs per API call. Retention period based on Postman plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mockIdYesThe mock server ID
limitNoMaximum number of logs to return (default: 100)
cursorNoPagination cursor
untilNoReturn logs until this timestamp
sinceNoReturn logs since this timestamp
responseStatusCodeNoFilter by response status code
responseTypeNoFilter by response type
requestMethodNoFilter by request method
requestPathNoFilter by request path
sortNoSort field
directionNoSort direction
includeNoInclude additional data (request.headers, request.body, response.headers, response.body)
Behavior3/5

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

Discloses maximum size and count per call and retention period, which adds value beyond the schema. However, no discussion of authentication, rate limits, or read-only nature. With no annotations, more detail is needed.

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?

Extremely concise: two sentences, no superfluous words. The verb is front-loaded and the key constraints are stated immediately.

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?

Given 12 parameters and no output schema, the description fails to summarize supported filters (status code, method, path, etc.) or explain pagination. It partially compensates with size limits.

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 100%, so the baseline is 3. The description does not add extra meaning to any parameter; it only provides global limits.

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 clearly states 'Get mock call logs', specifying the verb and resource. It distinguishes from sibling get/list tools by focusing on logs for a specific mock, and adds limits and retention info.

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?

No explicit guidance on when to use this tool versus alternatives like 'get_mock' or 'list_mocks'. Usage is implied but not differentiated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/delano/postman-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server