Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

beel_list_request_logs

Read-onlyIdempotent

Retrieve your public API request history across all your keys in the current environment, filter by time, key, method, status, or path to debug and audit calls.

Instructions

Returns the history of public API requests made by you, with any of your API keys in this environment — not only the key you are authenticating with. Only auth_type=API_KEY traffic is recorded.

  • The axis is the person, not the individual credential: a second key of yours sees the same history, and narrowing it to one key is a filter (api_key_id), not the default.

  • It is still not the account's traffic: requests made by other users of the same account, or by their API keys, are never returned. The {account_id} in the path authorizes the call; it does not widen what you can see.

  • Environment is not a filter: results are always scoped to the environment of the credential you authenticate with — a beel_sk_test_* key sees the test traffic of all your test keys, a beel_sk_live_* key the live traffic of all your live ones. To see the other environment, use a key from that environment.

  • Cursor pagination: navigate with the opaque cursor returned in next_cursor / prev_cursor; there is no jump to an arbitrary page N.

  • Time window: defaults to the last 30 days; narrow or move it with from/to.

Endpoint: GET /v1/accounts/{account_id}/request-logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoUpper bound of the time range (inclusive). Defaults to now.
fromNoLower bound of the time range (inclusive). Defaults to 30 days ago.
limitNoMaximum number of log entries in the page, from 1 to 100. Defaults to 25.
cursorNoOpaque cursor returned by a previous response (next_cursor / prev_cursor).
methodNoFilter by HTTP method.
account_idYesAccount the call is authorized against. It does not widen the result set.
api_key_idNoNarrow the result to one of your API keys. Any key of yours in this environment is accepted, not just the one you authenticate with; a key belonging to someone else simply yields no results.
http_statusNoFilter by an exact HTTP status code.
only_errorsNoIf true, only requests with status >= 400.
path_containsNoCase-insensitive substring of the actual request path, IDs included (for example `/v1/companies/3f1c9a2e-5b7d-4e8f-9a1b-2c3d4e5f6a7b/invoices/8a2b4c6d-1e3f-4a5b-8c7d-9e0f1a2b3c4d/send`), so a path template with `{placeholders}` never matches, and a full path only matches requests made to that exact route shape. Prefer a resource segment such as `/invoices`, which matches that resource on every route that serves it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of log entries in the page, from 1 to 100. Defaults to 25."
    • changedInput schema / properties / path_contains / description
      Previous value: -"Filter by path substring (case-insensitive)."New value: +"Case-insensitive substring of the actual request path, IDs included (for example `/v1/companies/3f1c9a2e-5b7d-4e8f-9a1b-2c3d4e5f6a7b/invoices/8a2b4c6d-1e3f-4a5b-8c7d-9e0f1a2b3c4d/send`), so a path template with `{placeholders}` never matches, and a full path only matches requests made to that exact route shape. Prefer a resource segment such as `/invoices`, which matches that resource on every route that serves it."
  2. Changed3 schema fields changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / method / example
      Removed value: -"POST"
    • removedInput schema / properties / path_contains / example
      Removed value: -"/v1/invoices"
  3. First observedv0.3.1

TDQS

A4.5/5.0
Behavior5/5

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

With annotations already covering read-only, idempotent, and open-world behavior, the description adds substantial behavioral context beyond them: only auth_type=API_KEY traffic is recorded, the result axis is the person rather than the credential, environment scope is tied to the authenticating key, pagination is cursor-based with no page-N jump, and the default time window is 30 days. These are concrete operational disclosures not available in the annotations.

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?

The description is front-loaded with the core purpose, then uses five bullets for distinct behavioral points. Each bullet addresses a separate concern (person axis, account scope, environment, pagination, time window) with little redundancy. It is somewhat lengthy, but the size is justified by the tool's subtle scoping rules.

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 10-parameter list tool with no output schema and safety annotations already present, the description covers the critical invocation context: scope, filters, pagination, defaults, and environment behavior. It does not describe the shape of individual log entries, which is a minor gap given the absence of an output schema, but an agent has enough to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description meaningfully adds beyond schema text: it explains that api_key_id is a narrowing filter rather than the default axis, and that account_id authorizes the call without widening the result set. It also clarifies that environment is not a filter parameter. These conceptual additions lift it above the baseline.

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 states a specific verb and resource: it returns the history of public API requests made by the authenticated user using any of their API keys in the same environment. It clearly distinguishes the scope from a single-credential view ("not only the key you are authenticating with") and limits it to API_KEY traffic. An agent can identify exactly what this tool does without opening the schema.

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 description gives explicit conditions: what traffic is included, that other users' requests are never returned, that environment is not a filter, and that to see the other environment one must use a key from that environment. It also covers cursor pagination and the default time window. However, it does not name or differentiate from the closest sibling, beel_get_request_log, so the when-to-use vs that alternative remains 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