What the connector exposes
The tools, prompts and resources the Trama MCP server hands your assistant — and the rules that decide which ones you get.
Once the connector is set up, your assistant sees a set of tools (things it can do), prompts (ready-made routines you can pick from your client's prompt menu) and resources (context it can read on its own).
Everything returns structured data rather than prose, which is what lets your assistant chain calls together instead of re-reading its own text.
Your role decides which tools you see. The server doesn't offer what you can't use: a sales rep never sees team performance, and without permission to take opportunities out of the funnel, archive and restore simply aren't in the list. This isn't a warning shown at call time — the tool isn't there.
Tools
Search
search_workspace — one call across opportunities, customers, conversations, catalogue and agents. Conversations are searched by content too, so a word said inside a thread finds it, and the result carries the fragment that matched. It's usually the first call: it resolves the id everything else asks for.
Opportunities
| Reading | Writing |
|---|---|
list_opportunities · get_opportunity · get_opportunities_board · query_opportunities · list_dormant_opportunities · list_paused_opportunities · list_archived_opportunities | create_opportunity · update_opportunity · move_opportunity · pause_opportunity · resume_opportunity · reactivate_opportunity · archive_opportunity · restore_opportunity · dispute_opportunity |
Follow-ups live here too: add_opportunity_follow_up, update_opportunity_follow_up and delete_opportunity_follow_up — logging one, correcting it, and taking back one that was logged by mistake.
query_opportunities is the analytical one: it counts and sums amounts grouped by rep, day, source, column or temperature, so "how much did we quote in July by rep" is one call rather than a walk over a list.
Customers
list_customers · search_customers · get_customer · get_customer_facts · create_customer · update_customer · update_customer_profile
get_customer_facts is the one worth knowing about: it returns what Trama learned about that person from their conversations, fact by fact, which is the difference between "here's a phone number" and "here's how this person buys".
Conversations
list_conversations · get_conversation · get_conversation_metrics · get_seller_response_gap
Conversations are read-only, by design. You can read one and summarise it; you can never reply to it or take it over from here.
And get_conversation returns the 50 most recent messages, not the whole thread. On a long conversation you're reading the tail. That cap exists because there's a third-party model on the other end of this connection, and reading a thread is not the same as exporting one.
Catalogue
list_catalog_products · get_catalog_product · create_catalog_product · update_catalog_product · publish_catalog_product · delete_catalog_product
Variants have their own set — list_product_variants, create_product_variant, update_product_variant, delete_product_variant, reorder_product_variants — and set_packages_on_link chooses what shows on your Offer Link.
Remember that publishing is what makes a product sellable: a created product is a draft until publish_catalog_product runs. That's the same rule as the catalogue screen.
Campaigns and ads
preview_campaign_audience · list_campaign_templates · get_campaign_proposals · draft_campaign_message · get_ad_performance
You can size an audience and draft the copy from here. Approving and sending stays in the dashboard — writing to your whole customer base is not a thing an assistant should be able to finish on its own.
Your pendings
list_pending_follow_ups · list_reminders · create_reminder · reschedule_reminder · resolve_reminder
This is the "what do I have today" surface — the same material as My day.
Questions from the agent
list_agent_questions · answer_agent_question
When the Inquiry Agent couldn't confirm something on its own, it asks the team. These two let you see what it's waiting on and answer it.
answer_agent_question is the one path by which something you write from here reaches a customer. Your answer goes back to the agent, and the agent uses it in the conversation. Everything else on this page stops inside Trama.
Team and organization
get_organization_overview · get_seller_performance · invite_member · set_member_assignable · set_member_spoken_languages
ask_trama
The catch-all: it asks the Trama Agent in natural language and gets an answer back. Use it for what no specific tool covers — compound requests, chained actions, or questions about how Trama itself works.
ask_trama is the only tool that draws on your plan's daily allowance, because it runs the Trama Agent. The rest are direct calls and cost nothing. If you hit the cap, the tool says so in its answer rather than failing.
The ones your client will double-check
Five tools are flagged as destructive in the protocol, which is what makes a well-behaved client ask you to confirm before running them:
archive_opportunity · dispute_opportunity · delete_opportunity_follow_up · delete_catalog_product · delete_product_variant
They're exposed rather than hidden — an assistant that can't archive is an assistant you stop using — but the flag is there so nothing with a wide blast radius happens silently.
Prompts
Your client shows these in its prompt menu (in Claude, the + next to the message box). They're routines we wrote so you don't have to phrase them:
| Prompt | What it does |
|---|---|
| revisar-mi-dia | Your pendings, reminders and yesterday's new opportunities, merged into one prioritized list |
| estado-del-embudo | Where the pipeline is jamming: which column piles up, which rep is overloaded, which source brings volume without conversion |
| barrido-de-seguimiento | Who to contact today and with what concrete excuse — it shows you the list before writing anything |
| como-viene-el-equipo | Board response times against the real ones measured on the conversations, and the gap between them |
| huecos-del-catalogo | Demand that shows up repeatedly and has no product covering it |
A prompt only appears if you have every tool it needs, so the menu you see matches your role too.
Resources
Two things your assistant can read without being told to:
trama://catalog— your organization's catalogue.trama://organization— the operational overview: members, channels, inbox, metrics.
They exist so the assistant has the shape of your business in hand before you ask anything, instead of spending a turn discovering it.