Skip to main content
Glama
7tg

django-admin-mcp

by 7tg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_article

Create a new Article in Django admin with required title, content, and author, plus optional inline rows. Specify data and inlines; any inline error rejects the whole call.

Instructions

Create a new Article, optionally with inline rows.

Date and datetime fields take a single ISO 8601 string (e.g. '2026-03-01' or '2026-03-01T09:30:00Z'). Foreign keys take the related object's ID, many-to-many fields a list of IDs. A field the admin form does not accept (unknown, read-only or non-editable) is rejected with an error, never ignored.

Fields:

  • id (BigAutoField)

  • title (CharField) [required]

  • content (TextField) [required]

  • author (ForeignKey) [required]

  • published_date (DateTimeField)

  • is_published (BooleanField)

  • created_at (DateTimeField)

  • updated_at (DateTimeField)

Input Schema

NameRequiredDescriptionDefault
dataYesThe data for the new Article
inlinesNoInline rows to create with the object, keyed by inline model name: {model_name: [{data}, ...]}. All-or-nothing: any inline error rejects the whole call and nothing is saved

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses format conventions (ISO 8601, FK by ID, M2M by ID list) and the rejection semantics for unknown/read-only/non-editable fields. Gaps remain around authentication requirements and side effects, so it is strong but not complete.

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?

Front-loaded with the purpose, followed by format rules and then the field list. Every section earns its place and there is no filler; the field enumeration is dense but informative.

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?

Input-side behavior is well covered, but with no annotations and no output schema, nothing anywhere states what a successful call returns or what permissions are needed. For a mutation tool with nested objects and inlines, those omissions leave the picture incomplete.

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 coverage is 100%, but the top-level 'data' param is a free-form object that the schema labels only as 'The data for the new Article'. The description adds real value by enumerating the fields with types and required markers, plus format rules that the schema does not express.

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?

The first sentence states a specific verb and resource ('Create a new Article') and adds scope ('optionally with inline rows'). It does not, however, differentiate itself from close siblings like update_article, which the agent must distinguish by name alone.

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?

There is no explicit when-to-use guidance, no prerequisites, and no named alternatives (e.g. update_article for existing records). Format guidance for dates and foreign keys is present, but that is parameter semantics rather than usage selection.

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

Deploy Server

Other Tools