Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_list_request_logs

Read-onlyIdempotent

Lists your API_KEY request history across all your keys in the current environment, with filters for time range, HTTP method, status, API key, and request path.

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.

BeeL API endpoint: GET /v1/accounts/{account_id}/request-logs (reference: https://docs.beel.es)

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": {
      "account_id": "<account_id>"
    },
    "name": "beel_list_request_logs"
  }
}

Input 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.6/5.0
Behavior5/5

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

Annotations already carry the read-only, idempotent safety profile, and the description goes well beyond them: log retention is limited to API-key traffic, the axis of visibility is the person rather than the credential, environment scoping follows the authenticating key, and pagination is cursor-only with no arbitrary page jump. These are non-obvious scoping rules an agent could not infer from structured fields.

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?

Front-loaded summary sentence followed by bolded bullets, each of which carries a distinct scoping rule. A few bullets restate schema defaults (cursor pagination, 30-day window), so there is minor redundancy, but the structure is easy to scan and nothing is padded.

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?

Ten parameters, no output schema, no nested objects — and the description covers the pagination contract through `next_cursor`/`prev_cursor` plus the scoping semantics of every dimension an agent could get wrong. Nothing needed to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds interpretation: `api_key_id` narrows rather than defaults, `cursor` is opaque with no page-N jump, and the time window defaults to 30 days movable via `from`/`to`. It says nothing about `method`, `http_status`, `only_errors`, or `path_contains` beyond what the schema already documents.

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 the history of public API requests') and immediately scopes it to the caller's keys in the current environment. That detail distinguishes it from beel_get_request_log (single entry), beel_list_email_deliveries and beel_list_webhook_deliveries without the agent needing to open sibling schemas.

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?

Explains when the tool applies ('Only `auth_type=API_KEY` traffic is recorded'), what it deliberately will not return (other users' requests on the same account), and how to reach the other environment (authenticate with a key from it). It does not name a sibling as an alternative or state exclusions such as when to prefer beel_get_request_log, which keeps it short of a 5.

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