Skip to main content
Glama

post_thread

Create discussion threads in Ed Discussion courses with markdown support for organizing course content and facilitating student engagement.

Instructions

Create a new discussion thread. Content can be markdown (auto-converted to Ed XML).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_idYesCourse ID
titleYesThread title
typeNoThread typepost
categoryYesCategory name
subcategoryNoSubcategory name
contentYesThread body (markdown or Ed XML)
is_privateNoPrivate thread
is_anonymousNoPost anonymously
is_pinnedNoPin the thread

Implementation Reference

  • The "post_thread" tool is defined and implemented in src/index.ts. It takes various thread details as input and uses the API client to post the thread.
    server.tool(
      "post_thread",
      "Create a new discussion thread. Content can be markdown (auto-converted to Ed XML).",
      {
        course_id: z.number().describe("Course ID"),
        title: z.string().describe("Thread title"),
        type: z.enum(["post", "question", "announcement"]).default("post").describe("Thread type"),
        category: z.string().describe("Category name"),
        subcategory: z.string().default("").describe("Subcategory name"),
        content: z.string().describe("Thread body (markdown or Ed XML)"),
        is_private: z.boolean().default(false).describe("Private thread"),
        is_anonymous: z.boolean().default(false).describe("Post anonymously"),
        is_pinned: z.boolean().default(false).describe("Pin the thread"),
      },
      async ({ course_id, title, type, category, subcategory, content, is_private, is_anonymous, is_pinned }) => {
        try {
          const result = await api.postThread(course_id, {
            type,
            title,
            category,
            subcategory,
            content: ensureEdXml(content),
            is_private,
            is_anonymous,
            is_pinned,
            is_megathread: false,
            anonymous_comments: false,
          });
          return ok(result);
        } catch (err) {
          return fail(err);
        }
      }
    );
Behavior3/5

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

With no annotations provided, description carries full burden. Adds valuable behavioral detail that markdown is 'auto-converted to Ed XML,' but fails to disclose mutation nature (persistence, visibility implications) or error conditions beyond what the schema boolean flags imply.

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?

Extremely efficient at two sentences. Front-loaded with primary action, second sentence provides essential format-specific implementation detail. No redundant or filler text.

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

Completeness3/5

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

Adequate for basic invocation with complete schema coverage, but gaps remain for a creation tool: no description of return values (thread ID? object?), success/failure indicators, or side effects like notifications triggered. Missing output schema increases burden on description.

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?

Schema has 100% coverage, establishing baseline 3. Description adds meaningful context that content is auto-converted from markdown to Ed XML, helping agents understand the content parameter's processing behavior beyond the schema's plain description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States 'Create a new discussion thread' with clear verb and resource. Distinguishes reasonably from siblings like post_comment and edit_thread through the term 'thread,' though could explicitly contrast with edit_thread or reply operations for maximum clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no guidance on when to use this versus post_comment (replies), edit_thread, or when anonymous/private posting is appropriate. No prerequisites mentioned (e.g., requiring valid course_id or category existence).

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/rob-9/edstem-mcp'

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