Skip to main content
Glama
semwalajay83-sem

salesforce-metadata-mcp

Create Agentforce Topic

sf_create_agent_topic
Idempotent

Create an Agentforce agent topic to define request scope and attach the action APIs it should execute. Must be called after creating actions and before creating the agent planner.

Instructions

Creates a Topic (GenAiPlugin) for an Agentforce Agent — step 3 of the agent setup sequence. Call this AFTER all actions have been created with sf_create_agent_action. CRITICAL: pass ALL action API names in the 'actions' array — omitting it creates a topic with no executable actions and the agent silently does nothing. agentName is informational only (not written to XML) — the actual agent→topic wiring happens in sf_create_agent_planner which you MUST call immediately after this step. Do not stop between steps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesTopic label
scopeYesScope of this topic — what kind of requests it handles
actionsNoCRITICAL: Action API names (from sf_create_agent_action) to link to this topic. If you omit this or pass an empty array, the topic is created with NO executable actions — the agent will silently do nothing for this topic. Always include all action API names here.
agentNameYesParent agent API name — informational only, NOT written to the topic XML. The actual agent→topic wiring happens in sf_create_agent_planner (required separate step).
topicNameYesTopic API name, e.g. 'OrderManagement'. Letters, numbers, underscores. This is the name you must include in topicNames when calling sf_create_agent_planner.
descriptionYesWhat this topic covers
instructionsNoStep-by-step instructions for handling this topic. Pass as a single string or an array of strings (each becomes a separate instruction entry).
Behavior5/5

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

Discloses a critical failure mode (omitting actions results in a silently non-functional topic), clarifies that agentName is informational only, and indicates that the actual wiring happens in a later step. This adds meaningful context beyond annotations like idempotentHint and readOnlyHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences that are front-loaded with the primary purpose, followed by critical warnings and sequence instructions. Every sentence earns its place with no redundant or filler content.

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?

The description provides the sequence position, prerequisites, critical parameter behavior, and the required next step, making it complete for standalone use even without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides 100% coverage with detailed parameter descriptions, including the CRITICAL warning about actions and the informational nature of agentName. The tool description reiterates these points but does not add new parameter-level meaning, so baseline 3 is appropriate.

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 explicitly states the tool 'Creates a Topic (GenAiPlugin) for an Agentforce Agent' and identifies itself as 'step 3 of the agent setup sequence,' clearly distinguishing it from sibling tools like sf_create_agent_action and sf_create_agent_planner.

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?

Provides explicit sequencing: 'Call this AFTER all actions have been created with sf_create_agent_action' and requires calling sf_create_agent_planner immediately after. It also warns 'Do not stop between steps,' giving strong workflow guidance and alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/semwalajay83-sem/salesforce-metadata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server