Skip to main content
Glama

create_session

Create a new exploratory testing session with optional tags, mission, estimate, and assignee to manage test activities.

Instructions

Create a new exploratory testing session. Requires write permission. mission accepts rich HTML (the high-level charter). assigneeUserId accepts either a User _id ("user_abc...") or an email address — the email is resolved against TestDino users automatically. estimate is in minutes. Findings cannot be created here — add them in the UI. IMPORTANT: tags must be a JSON array of strings — e.g. ["exploratory","auth"] — NOT the comma-separated form that list_sessions accepts as a filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSession name (required).
tagsNoArray of tag strings, e.g. ["exploratory","auth"]. NOT a comma-separated string.
stateNoWorkflow state (default 'new'). Either canonical ('under_review') or display ('Under review') form — server normalizes to lowercase+underscored so UI colors render correctly.
configNo
missionNoRich HTML mission/charter.
estimateNoEstimate in minutes.
projectIdYesProject ID (required).
releaseIdNoAttach session to this release.
attachmentsNoArray of attachment objects or URLs.
environmentNo
sessionTypeNoFree-text type, e.g. 'Exploratory'.
linkedIssuesNoArray of linked-issue objects.
assigneeUserIdNoUser _id ("user_abc...") OR email address — both accepted. Email is looked up server-side.
Behavior4/5

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

No annotations provided, but description covers write permission, rich HTML for mission, minutes for estimate, dual input for assigneeUserId, state normalization, and tags format. Lacks mention of return value or error behavior.

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

Conciseness4/5

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

Well-structured with key details front-loaded, but could be more concise with bullet points. No redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers most critical aspects given 13 parameters and no output schema, but lacks return value description and error handling details.

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

Parameters5/5

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

Adds significant value beyond schema: explains rich HTML for mission, email resolution for assigneeUserId, minutes for estimate, display vs canonical state forms, and provides explicit tags examples with a warning against comma-separated strings.

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?

Clearly states it creates a new exploratory testing session, differentiating from sibling create tools like create_manual_run or create_release.

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?

Explicitly states permission requirement, clarifies that findings cannot be created via this tool, and warns about the tags format difference from list_sessions, guiding correct usage.

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/testdino-hq/testdino-mcp'

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