Skip to main content
Glama
Degree-AS
by Degree-AS

dw_api_call

Make raw calls to DynamicWeb Admin API endpoints. Supports GET and POST with three body modes: model, raw, or update for creating, deleting, or updating records.

Instructions

Make a raw call to any DynamicWeb Admin API endpoint. For GET: provide params as query params. For POST: choose bodyMode. - 'model' (default) — wraps your model in {"Model": ...}. Used by most Save endpoints that create new records. - 'raw' — sends your model as the top-level body (no wrapper). Used by delete-style commands (e.g. ProductDelete, ItemTypeDelete). Supports params in the URL. - 'update' — sends {RunUpdateIndex?, QueryData, model} and appends ?Query.Type=queryType. Used to UPDATE existing records via screen commands (e.g. ProductSave). For update mode: pass queryType (e.g. 'ProductById'), queryData (identifies the record: {Id, LanguageId, QueryContext:{screenTypeName:'ProductEdit'}}), and optionally extraFields (e.g. {RunUpdateIndex:true}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointYesEndpoint name without leading slash, e.g. 'NavigationAll'
methodNoGET
paramsNoQuery parameters (used by GET and POST-raw)
modelNoBody for POST
bodyModeNoHow to wrap the body: 'model' | 'raw' | 'update'model
queryTypeNoRequired for bodyMode='update'. E.g. 'ProductById', 'ProductsAll'
queryDataNoRequired for bodyMode='update'. Identifies the record, e.g. {Id:'PROD1', LanguageId:'LANG1', QueryContext:{screenTypeName:'ProductEdit'}}
extraFieldsNoExtra top-level body fields for bodyMode='update' (e.g. {RunUpdateIndex:true})
Behavior4/5

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

No annotations are provided, so the description carries full burden. It transparently explains the three body modes, their wrapping behavior, and how parameters like queryType and queryData are used in update mode. It does not disclose potential side effects or idempotency, but covers the essential behavioral details for a raw API call.

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?

The description is fairly long but well-structured with bullet points for the three body modes. It front-loads the overall purpose in the first sentence. However, there is some redundancy in listing and describing each mode, and could be slightly more concise.

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?

The tool has 8 parameters with complex behavior across three modes. The description covers all modes, explains each parameter's context, and gives examples. It lacks description of the return value (no output schema), but given the tool's generic nature, the response is variable. Overall, it is fairly complete for the complexity level.

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?

With 88% schema coverage, the description adds significant meaning beyond the input schema. It clarifies how parameters interact (e.g., queryType and queryData are required for update mode, extraFields adds top-level fields), and provides context for each parameter's role. For example, 'params' are described as used by GET and POST-raw, and bodyMode alternatives are explained with examples.

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 the tool's purpose as making a raw call to any DynamicWeb Admin API endpoint, using a specific verb ('Make') and resource ('raw call to any DynamicWeb Admin API endpoint'). It distinguishes itself from sibling tools by being the generic raw call tool, while siblings are specialized for specific operations.

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

Usage Guidelines4/5

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

The description provides detailed context on when to use each bodyMode (model for saves, raw for deletes, update for updates) and specifies that GET uses params and POST uses bodyMode. It gives explicit examples for each mode, but does not explicitly mention when to use sibling tools instead of this generic call.

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/Degree-AS/degree-dynamicweb-mcp'

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