Skip to main content
Glama

Agent Manage Tool

agent_manage
Destructive

Manage AI agents: create, list, update, delete, and toggle status. Browse pre-built agent templates.

Instructions

Core CRUD for AI agents in the caller's team. For runtime inspection, rollback, skill/tool wiring or feedback use agent_advanced. provider and model are validated against team-configured BYOK and local-LLM credentials at create/update time.

Actions:

  • list (read) — optional: status, limit (default 50), cursor.

  • get (read) — agent_id.

  • create (write) — name, role, goal; optional: backstory, provider, model, skill_ids[], tool_ids[].

  • update (write) — agent_id + any creatable field. Partial updates allowed.

  • delete (DESTRUCTIVE) — agent_id, confirm=true. Soft-deletes; recoverable for 30 days.

  • toggle_status (write) — agent_id. Flips active ↔ disabled.

  • templates (read) — pre-built agent templates from the platform catalog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: list, get, create, update, delete, toggle_status, templates
deadline_msNoOptional: max wall-clock time (ms) the tool may spend. If exceeded during the call, returns a DEADLINE_EXCEEDED error. Minimum 100 ms. Leave unset for no deadline.
statusNoFilter by status: active, disabled
scopeNoFilter by scope: team, personal
limitNoMax results to return (default 10, max 100)
agent_idYesThe agent UUID
nameYesAgent name
roleNoAgent role description
goalNoAgent goal
backstoryNoAgent backstory
providerNoLLM provider key (e.g. anthropic, openai, google, claude-code). Defaults to platform default.
modelNoLLM model name. Defaults to platform default.
personalityNoAgent personality traits: {tone, communication_style, traits[], behavioral_rules[], response_format_preference}
data_classificationNoData classification level: public, internal, confidential, restricted. Confidential and restricted agents are routed to local-only providers.
tool_profileNoTool profile restricting tool access. Options: researcher, executor, communicator, analyst, admin, minimal
environmentNoEnvironment preset that auto-attaches a tool bundle. Options: minimal, coding, browsing, restricted.
reasoning_effortNoExtended thinking effort (Anthropic). Options: none, low, medium, high, auto. "auto" lets the platform pick by task complexity.
use_tool_searchNoEnable semantic tool auto-discovery — at run time, up to tool_search_top_k matching tools from the team pool are auto-attached based on the user prompt.
tool_search_top_kNoMaximum tools tool_search will surface per run (1–20, default 5). Only applies when use_tool_search=true.
sandbox_profileNoJSON string defining Docker sandbox profile for per-execution process isolation (enterprise only). Example: {"image":"python:3.12-alpine","memory":"512m","cpus":"1.0","network":"none","timeout":300}
knowledge_base_idNoUUID of a knowledge base to link to this agent for RAG-powered context
evaluation_enabledNoEnable A/B evaluation for this agent
evaluation_sample_rateNoFraction of requests to include in evaluation (0.0 to 1.0). Only used when evaluation_enabled is true.
heartbeat_definitionNoAgent health check config: {enabled: bool, cron: string, prompt: string}
budget_cap_creditsNoPer-agent budget cap in credits. Set to 0 to remove cap.
thinking_budgetNoAnthropic extended thinking budget in tokens (e.g. 1024, 4096, 8192). Only applies when agent provider is "anthropic". Set to 0 to disable. Enables chain-of-thought reasoning visible in experiment steps.
confirmYesMust be true to confirm deletion. This is a destructive action.
categoryNoFilter by category: engineering, content, business, design, research
Behavior5/5

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

Annotations only provide `destructiveHint=true`. The description goes well beyond by detailing that delete is destructive and performs a soft-delete recoverable for 30 days, mentions validation of provider/model at creation/update, and notes that partial updates are allowed. No contradictions with annotations.

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?

The description is front-loaded with the core purpose and sibling differentiation. It then uses a concise bullet list to detail each action, with no extraneous information. Every sentence earns its place.

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?

Despite having 28 parameters, no output schema, and complex nested objects, the description covers all key behaviors: CRUD actions, validation, soft-delete, and defaults. It gives sufficient context for an AI agent to select and invoke the tool correctly.

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?

The input schema has 100% description coverage, but the description adds value by grouping parameters into actions, explaining defaults (limit default 10, max 100), and clarifying that `confirm=true` is required for deletion. It also states validation of provider/model at create/update time, which is not in the schema. This goes beyond baseline.

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 clearly states 'Core CRUD for AI agents in the caller's team' and enumerates all seven actions (list, get, create, update, delete, toggle_status, templates). It also distinguishes itself from the sibling tool `agent_advanced` by specifying what that sibling is for, making purpose unambiguous.

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?

The description explicitly tells when to use this tool versus `agent_advanced` ('For runtime inspection, rollback, skill/tool wiring or feedback use `agent_advanced`'). It also gives a brief overview of each action, guiding the agent on when to invoke which action.

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/escapeboy/agent-fleet-o'

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