Browse email template summaries with a regional workspace key. No content retrieval, sending or template changes.
What you can do (2)
What you can do
Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List email template summaries — bird.templates.list |
Read |
Get email template summary — bird.templates.get |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Bird, then enter the issued values in the connection form below.
- In your Bird dashboard, open Platform tools > API keys and create a workspace API key with email_management at read level. Copy the full key when shown; lost keys must be rotated. In My tools, open Bird, choose Use my provider credentials, paste it into Bird workspace API key, select the template read commands and save. The bk_us1_ or bk_eu1_ prefix selects the official US or EU API host automatically. This current Bird API does not use legacy Connectivity Platform AccessKey credentials. List templates with limit=20 and scope=workspace or system, then pass next_cursor as starting_after for another explicit page; get a template by ID or slug. Summaries do not read content, send messages or change templates. Disconnect here and revoke or rotate the key in Bird when finished.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Bird workspace API key | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"limit": 20,
"scope": "workspace"
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
List email template summaries — bird.templates.list
Read one explicit page of email template names, IDs, scope, category, status and default language. Use the returned next_cursor as starting_after to continue; no content retrieval, message sending or template changes.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.limit |
integer | Required | Requested page size; choose 20. The existing response byte budget applies. | minimum: 1; maximum: 9007199254740991 |
query.scope |
string | Required | Template owner scope. | enum: ["workspace","system"] |
query.starting_after |
string | Optional | Opaque cursor from the preceding response; omit on the first page. | maxLength: 8192; pattern: "^[\\x21-\\x7e]{1,8192}$" |
Full JSON Schema
Example input
{
"query": {
"limit": 20,
"scope": "workspace"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Get email template summary — bird.templates.get
Read summary metadata for a known template ID or slug, including built-in bird_ system slugs. No template body, editor links, recipients, sends or writes.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.template_ref |
string | Required | Existing template ID or slug. | maxLength: 512; pattern: "^[A-Za-z0-9_-]+$" |
Full JSON Schema
Example input
{
"path": {
"template_ref": "welcome-email"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.