Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_sens_list_brandmessage_templates

Read-only

Retrieve Brand Message templates for a KakaoTalk channel, filtering by type, code, or name, with pagination to manage and review existing templates.

Instructions

List Brand Message templates of a channel (GET /brandmessage/v2/services/{serviceId}/templates). Note the channel parameter is plusFriendId here (Alim Talk uses channelId). Returns { items[], totalCount, hasNext }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageSizeNoItems per page (1-100, default 100)
pageIndexNoPage index (0-based, default 0)
serviceIdNoBiz Message service ID in NRN form (e.g. ncp:kkobizmsg:kr:1********2:myproject). Defaults to NCLOUD_SENS_BRANDMESSAGE_SERVICE_ID (or NCLOUD_SENS_ALIMTALK_SERVICE_ID) / NCLOUD_SENS_SERVICE_ID. Find it with ncloud_sens_list_projects (kkoBizMsgService.serviceId). A 'Forbidden' reply means the project does not have this channel enabled.
messageTypeNoFilter by message type
plusFriendIdYesKakaoTalk channel ID (e.g. @channelname)
templateCodeNoFilter by template code
templateNameNoFilter by name (full or partial match)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already provide readOnlyHint; the description adds the GET endpoint and the response structure, which is a clear context for the caller.

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 a concise 2-sentence structure with a clear first sentence.

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?

The context is complete for a typical read-only list operation. The response shape is already described.

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?

Schema description coverage is 100%, so the parameter descriptions are present. The note about plusFriendId vs channelId appears to the schema's role. The description doesn't add much new.

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 ('List Brand Message templates of a channel'), adds the HTTP endpoint path, and the plusFriendId/channelId distinction makes it easy to tell apart from the AlimTalk template resource.

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?

It gives the context that the channel parameter is plusFriendId here and AlimTalk uses channelId, which implicitly signals which is correct list to use. It does not explicitly name an alternative tool or state conditions for when this tool is preferred overused for the rest.

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