Agent tools
List an agent's tools
Every action and MCP tool this agent could use, plus the Lelemon system tools (transfer_to_human, save_case_data, send_buttons, send_list, send_products, send_carousel, send_cta_url, send_flow, request_location, ask_team, check_availability, schedule_meeting and cancel_meeting), with granted saying which ones it may use now. Newest first, system tools last. For a granted transfer_to_human or save_case_data, config holds how it was set up; the other system tools take no config. Other Lelemon built-in tools and connectors are not listed here.
Required scope: actions:read.
path Parameters
id^agt_[0-9A-Za-z]{22}… · requiredThe id of the agent (agt_…).
query Parameters
limitcursorThe nextCursor of the previous page, with the same filters.
grantedtrue: only what the agent may use. false: only what it could use but has not been granted.
Headers
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
List an agent's tools › Responses
objecthasMorenextCursorGrant a tool
Lets the agent use an action (act_), an MCP tool (mtl_) or a system tool. Use it to give the agent the ability to hand a case to a person (path value transfer_to_human), to write the case fields whose source is agent (path value save_case_data), or to send interactive WhatsApp messages (path value send_buttons for up to 3 reply buttons, send_list for a menu of 4 to 10 options, send_products for catalog products, send_carousel for 2 to 10 swipeable cards, send_cta_url for one link button, send_flow to open a WhatsApp Flow, request_location to ask for a shared location). To let the agent book and cancel meetings on your default agenda, grant check_availability, schedule_meeting and cancel_meeting (they take no config, and the agenda has to be set up first). One tool at a time, so two people granting at once do not undo each other. Idempotent: granting twice with the same body changes nothing. For a system tool, config replaces the stored one and leaving it out clears it; transfer_to_human takes stageId, businessHours and farewell, save_case_data takes fields. For an action or MCP tool, approval puts it behind a person (see GET /v2/approvals): leaving it out keeps the current policy, mode never lifts it. To let the agent ask your team without handing over the case, grant ask_team (answers go through POST /v2/team-questions/{id}/answer). A handed-over case fires case.escalated and moves to human control.
Required scope: actions:write.
path Parameters
id^agt_[0-9A-Za-z]{22}… · requiredThe id of the agent (agt_…).
toolId^(?:act_[0-9A-Za-z]{… · requiredAn action (act_…), an MCP tool (mtl_…), a data connector tool (dct_…) or a system tool name such as transfer_to_human.
Headers
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
Grant a tool › Request Body optional
Only for the system tools transfer_to_human and save_case_data. It replaces the stored configuration: leaving it out clears it. Actions and MCP tools take no configuration.
Only for actions and MCP tools. Puts the tool behind a person: the agent proposes, a person or a named API key decides, and only an approval runs the action. Leaving it out keeps the policy the tool already has, so granting again never lifts it. To lift it, send mode never.
Grant a tool › Responses
objectidact_ for an action, mtl_ for an MCP tool, dct_ for a data connector tool, the tool name itself for a system tool. Use it in the path of PUT and DELETE.
kindnamedescriptiongrantedTrue when this agent may use it now.
serverIdFor an MCP tool, the server it comes from.
sharedByPlatformFor an action or an MCP tool: true when it belongs to your platform and is shared with your subaccounts. Absent for system tools and your own.
connectorIdFor a data connector tool (dct_), the data connector it reads. Only internal agents, such as a support copilot, can be granted them.
For a granted system tool, its configuration. Null when it has none. Absent for actions and MCP tools.
The approval policy of an action or MCP tool for this agent. mode never when it runs without approval. Absent for system tools.
The minimum approval your platform set for this shared action (PUT /v2/actions/{id}/approval-floor). It applies on top of approval: the stricter one wins, and approval cannot be mode never. Absent when there is none.
Remove a tool
The agent stops using it. The action or MCP tool itself stays; for a system tool its configuration is deleted. Removing a tool the agent did not have is not an error.
Required scope: actions:write.
path Parameters
id^agt_[0-9A-Za-z]{22}… · requiredThe id of the agent (agt_…).
toolId^(?:act_[0-9A-Za-z]{… · requiredAn action (act_…), an MCP tool (mtl_…), a data connector tool (dct_…) or a system tool name such as transfer_to_human.
Headers
Lelemon-Subaccount^sub_[0-9A-Za-z]{22}…The subaccount (sub_…) this request acts on. Only for the keys of a platform account; without it the request acts on the account itself.
Remove a tool › Responses
Removed.