Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

resend_topic

Read-only

Resend topics, read-only — the subjects a contact opts in to or out of (e.g. "Product updates"), shown to the recipient on the unsubscribe page. The RECIPIENT changes their subscription; one contact's subscriptions are in resend_contact(op="get"). A Broadcast scoped to a topic skips the contacts who opted out of it.

op: "list" (default) the account's topics, paginated (limit, after); "get" one topic (topic_id).

Needs a Resend key with Full access (a sending-only key is refused). Returns — list: {topics: [{id, name, description, default_subscription, visibility, created_at}], has_more, next_after}; get: the topic.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resend_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNolist (default) | get.list
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
fullNoResend's raw response instead of the trimmed view.
afterNoop="list" — cursor: the `next_after` of the previous page.
limitNoop="list" — page size, 1 to 100 (default 50).
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
topic_idNoop="get" — the topic id.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: a Full-access Resend key is required and a sending-only key is refused. It stops short of deeper behavior such as rate limits or what 'default_subscription' and 'visibility' values mean.

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-loads the identity and read-only nature, then op semantics, then prerequisites, then return shape — a sensible order. A few phrases ('shown to the recipient on the unsubscribe page') are illustrative rather than operational, but nothing is materially wasteful.

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 no output schema, the description carries the return contract and does so explicitly for both ops, including has_more and next_after for pagination. Auth requirements and the sibling cross-reference close the remaining gaps; only the meaning of individual topic fields is left implicit.

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. The description still earns a notch above by tying parameters to operations ('list' takes limit/after, 'get' takes topic_id) and framing `after` as the cursor from the previous page's next_after, which clarifies the pagination loop rather than just restating the schema.

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?

Opens with a specific verb and resource ('Resend topics, read-only') and defines the domain object in concrete terms ('the subjects a contact opts in to or out of'). It explicitly distinguishes the resource from the sibling resend_contact by stating that per-contact subscriptions live there, so an agent can route without opening either schema.

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 explicit routing guidance: the recipient changes their subscription, one contact's subscriptions are in `resend_contact(op="get")`, and it explains the downstream effect that a Broadcast scoped to a topic skips opted-out contacts. It doesn't spell out when to choose list vs get beyond the op definitions, but that choice is self-evident from the enum.

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

All Tulina toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources