Skip to main content
Glama
BeeL MCP server

BeeL MCP server

Official
by beel-es

beel_get_email_delivery_indicators

Read-onlyIdempotent

Returns email counts, latest delivery status, and last sent time for specified related entity IDs, letting you show an entity's email state without loading its full history.

Instructions

Returns, for each related entity id given, how many emails the history holds for it, the status of the most recent one and when it was sent. Lets you show the state of an entity's email without loading its full history.

  • last_status: carries whatever the latest attempt ended in, REJECTED and QUEUED included, so a count above zero does not mean an email reached anyone.

  • Ids with no associated emails: omitted from the response rather than returned with count 0.

Closed catalogue. This collection is fixed and bounded by the request itself — at most one indicator per id in related_entity_ids: it carries no pagination, it takes no page/limit, and every response holds the whole set.

BeeL API endpoint: GET /v1/accounts/{account_id}/email-indicators (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>",
      "related_entity_ids": "<related_entity_ids>"
    },
    "name": "beel_get_email_delivery_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesYour own account, or an account you provisioned. It — not the credential — decides which account the operation acts on; a `403` is returned when you do not reach it, the same response an account that does not exist gets.
related_entity_idsYesComma-separated list of related entity ids (e.g. invoice ids)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.3.1

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, and the description still adds substantive behavior: last_status can be REJECTED or QUEUED so count>0 does not mean delivery, and ids without emails are omitted rather than returned with count 0. That omission rule is the kind of detail an agent would otherwise get wrong.

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 tight bullets on status semantics and omission, then the closed-catalogue note. The closed-catalogue paragraph restates the same point three ways ('no pagination', 'no page/limit', 'whole set'), a minor redundancy.

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?

With only two required params, no output schema and no nested objects, the description covers the return concepts (count, last_status, sent time) and the sparse-response behavior well. It does not enumerate the response envelope, but the annotations and schemas carry little else that needs explaining.

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 cardinality meaning for related_entity_ids — at most one indicator per requested id — and clarifies the response can be shorter than the request. That is meaning beyond the schema's 'comma-separated list of related entity ids'.

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: for each related entity id it returns email count, the most recent delivery status, and when it was sent. The phrase 'without loading its full history' implicitly contrasts it with the per-delivery listing tools, though no sibling is named outright, keeping it short of a 5.

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?

Gives a clear use case — summarizing an entity's email state without pulling the full history — which is exactly the selection criterion against beel_list_email_deliveries/beel_get_email_delivery. It stops short of an explicit when-not or named-alternative statement.

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