Skip to main content
Glama
Sign In
@zients/line-mcp-server

@zients/line-mcp-server

by zients
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Sent Push Message Count

get_sent_push_count

Retrieve the count of push messages sent on a specific date using yyyyMMdd format. Query LINE messaging analytics to monitor your push campaign performance.

Instructions

Get the number of push messages sent on a specified date.

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_sent_push_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate in yyyyMMdd format (e.g. 20240101). Must be exactly 8 digits. Timezone: UTC+9

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It indicates a read operation but does not disclose potential errors, rate limits, or side effects, leaving some behavioral aspects unclear.

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, clear sentence with no unnecessary words, and it directly follows the tool's purpose.

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?

For a simple query tool, the description provides sufficient context. No output schema is present, and the parameter format is already specified in the schema, so nothing essential is missing.

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 provides detailed parameter description (format, timezone). The tool description only reiterates 'specified date' and adds no new meaning, so it meets the baseline for high schema coverage.

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 the specific action (get number) and the resource (push messages sent on a date), making it distinguishable from sibling tools like get_sent_reply_count or get_sent_broadcast_count.

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?

The description does not explicitly mention when to use this tool over alternatives. The name and context imply it, but explicit guidance is absent.

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