Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MT_API_URLYesURL to mt-data-api.cgi
MT_PASSWORDYesWeb Services Password from MT user profile
MT_REMEMBERNoRemember flag (0/1). Leave at 1 to keep sessions active.1
MT_USERNAMEYesMovable Type username
MT_CLIENT_IDYesClient identifier composed of letters, _, or -
MT_API_VERSIONYesData API version (e.g., 5, 6, 7)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_draftA

Movable Typeに新しい下書き記事を作成します。作成した記事は自動的にセッションに記憶され、update_last_draftで編集可能になります。

update_last_draftC

最後に作成または編集した下書き記事を更新します。タイトル、本文、タグなどを部分的に更新できます。

update_draftB

指定したIDの下書き記事を更新します。明示的に記事IDを指定して編集したい場合に使用します。

get_draftC

指定したIDの下書き記事の詳細を取得します。

list_recent_draftsB

最近の下書き記事の一覧を取得します。記事IDやタイトルを確認できます。

list_sitesA

利用可能なブログ(サイト)の一覧を取得します。blog_idを確認する際に使用します。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have distinct roles (get, list, create, update, list_sites). update_last_draft and update_draft have overlapping functionality, but descriptions clearly differentiate session-based vs explicit-ID updates, making confusion unlikely.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (get_draft, list_recent_drafts, create_draft, update_last_draft, update_draft, list_sites). The convention is predictable and readable throughout.

Tool Count5/5

Six tools is well-scoped for a Movable Type draft management server. Each tool serves a clear purpose: create, read, list, update (two variants for convenience), and site listing for context.

Completeness4/5

Core draft lifecycle operations (create, read, list, update) are well covered, plus site listing. Minor gaps include no delete or publish operation and no explicit site/blog_id parameter on create_draft, but these are not critical for a draft-writing tool.

Maintenance

ActivityInactive
ResponsivenessNo issues