@zients/line-mcp-server

Get Message Deliveries

get_message_deliveries

Get message delivery counts for any date (yyyyMMdd) with breakdowns by API type to analyze LINE messaging performance.

Instructions

Get the number of message deliveries on a specified date, including breakdowns by API type.

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": {
      "date": "<date>"
    },
    "name": "get_message_deliveries"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes	Date in yyyyMMdd format (e.g. 20240101). Must be exactly 8 digits. Timezone: UTC+9

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Sep 4, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states what the tool does but does not mention timezone handling (beyond schema), rate limits, authentication requirements, or the structure of the breakdown. For a read-only tool, this is a minimal but not comprehensive disclosure.

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?

The description is a single sentence that is both concise and front-loaded with the core purpose. Every word adds value, and it avoids redundancy with the schema.

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?

The tool has one parameter and no output schema. The description mentions 'breakdowns by API type' but does not explain the format or fields of the response. While an agent can infer the basic purpose, the lack of guidance on response structure or usage conditions leaves some gaps, though it is not severely incomplete for a simple query tool.

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?

The schema already fully describes the single 'date' parameter with pattern, example, and timezone, achieving 100% schema coverage. The description adds no additional parameter meaning beyond the schema, so the baseline of 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?

States a clear verb (Get), resource (number of message deliveries), and specific qualifiers (on a specified date, breakdowns by API type). It is distinct from sibling tools like get_sent_push_count, which count sends, not deliveries, and clearly conveys its scope.

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

Usage Guidelines2/5

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

Provides no guidance on when to use this tool versus alternatives. It does not mention which sibling tools it overlaps with or when one would choose this over get_sent_reply_count or get_statistics_per_unit. The agent is left to infer usage from the name and description.

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

Deploy Server