> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-in-ai/17.latest/mcp/base-mcp/sdk/constants.md).

# Constants

The SDK exports well-known Umbraco IDs for media types, user groups, data types, and member types. These are hardcoded constants from the Umbraco source code, stable across all installations. Use them instead of hardcoding GUIDs in your tools.

## Available Constants

### General

* `BLANK_UUID` — a zero UUID, used as a placeholder or default value

### Media Types

IDs and display names for the standard Umbraco media types:

* `FOLDER_MEDIA_TYPE_ID`, `IMAGE_MEDIA_TYPE_ID`, `FILE_MEDIA_TYPE_ID`, `VIDEO_MEDIA_TYPE_ID`, `AUDIO_MEDIA_TYPE_ID`, `ARTICLE_MEDIA_TYPE_ID`, `VECTOR_GRAPHICS_MEDIA_TYPE_ID`
* `MEDIA_TYPE_FOLDER`, `MEDIA_TYPE_IMAGE`, `MEDIA_TYPE_FILE`, `MEDIA_TYPE_VIDEO`, `MEDIA_TYPE_AUDIO`, `MEDIA_TYPE_ARTICLE`, `MEDIA_TYPE_VECTOR_GRAPHICS`
* `STANDARD_MEDIA_TYPES` — a lookup map from display name to media type ID

### User Groups

* `TRANSLATORS_USER_GROUP_ID`, `WRITERS_USER_GROUP_ID`

### Data Types

* `TextString_DATA_TYPE_ID`, `MEDIA_PICKER_DATA_TYPE_ID`, `MEMBER_PICKER_DATA_TYPE_ID`, `TAG_DATA_TYPE_ID`

### Member Types

* `Default_Memeber_TYPE_ID`

## Usage

Import the constants you need from the SDK:

```typescript
import {
  IMAGE_MEDIA_TYPE_ID,
  MEDIA_TYPE_IMAGE,
  STANDARD_MEDIA_TYPES,
} from "@umbraco-cms/mcp-server-sdk";
```

Use them in your tool handlers instead of hardcoding GUIDs. For example, when filtering media by type:

```typescript
if (item.mediaType.id === IMAGE_MEDIA_TYPE_ID) {
  // Handle image-specific logic
}
```

Or look up a media type ID from its display name:

```typescript
const mediaTypeId = STANDARD_MEDIA_TYPES["Image"];
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.umbraco.com/umbraco-in-ai/17.latest/mcp/base-mcp/sdk/constants.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.