Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

resend_segment

Resend segments — the groups of contacts a Broadcast is sent to. A segment is internal: recipients never see its name. Its members are read with resend_contact(op="list", segment_id=…); a contact joins one through resend_contact(op="upsert", segment_ids=[…]) or op="add_to_segment".

op: "list" (default) the account's segments, paginated (limit, after); "get" one segment (segment_id); "create" a segment (name). No delete here: a segment is removed from the Resend dashboard.

Needs a Resend key with Full access (a sending-only key is refused, and the error says how to fix it). Returns — list: {segments: [{id, name, created_at}], has_more, next_after}, pass next_after as after for the next page, full=true returns Resend's raw page; get: the segment; create: {id, name}, or {dry_run, would_create}.

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

Input Schema

NameRequiredDescriptionDefault
opNolist (default) | get | create.list
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
fullNoop="list"/"get" — Resend's raw response instead of the trimmed view.
nameNoop="create" — the segment name.
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.
dry_runNoop="create" — preview, no call.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
segment_idNoop="get" — the segment id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does: it discloses the credential requirement (Full access key, a sending-only key is refused with a fixable error), states that a segment name is internal and never shown to recipients, and specifies exact return shapes per op including pagination via `has_more`/`next_after` and the `dry_run` preview result. The absence of a delete path is also stated outright rather than left to be discovered.

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 opening sentence defines the resource, the middle paragraph front-loads the op semantics, and the final paragraph covers auth and returns, so structure is strong and each block is purposeful. It is on the long side for a tool description, but almost every clause carries operational information rather than filler.

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 12-parameter, no-annotation, no-output-schema tool, the description supplies the auth prerequisite, the per-op return contract, pagination mechanics, and the missing-delete caveat, which are exactly the things structured fields cannot convey. The remaining scoping parameters are documented in the schema itself at full coverage, so nothing an agent needs to call this correctly is absent.

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 description coverage is 100%, so the baseline is 3, and the description earns above that by explaining behavior the schema only labels: `after` is fed from the previous page's `next_after`, `full=true` yields Resend's raw page rather than the trimmed view, and `dry_run` makes create a no-call preview. The org/project/run scoping parameters are left entirely to the schema, which is the only real gap.

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 names the specific resource (segments, the groups of contacts a Broadcast targets) and states precisely which operations exist. It explicitly separates this tool from `resend_contact`, which handles membership, so an agent can distinguish it from its nearest sibling 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 Guidelines5/5

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

It gives an op-by-op routing table (list is default and paginated, get needs segment_id, create needs name) plus explicit exclusions: there is no delete here, deletion happens in the Resend dashboard, and membership changes go through `resend_contact`. That is when-to-use, when-not-to-use, and named alternatives all in one place.

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